Why iMessage speech messages swallowed with Ben & Jerry’s

Anyone who asks to get an ice cream from Ben & Jerry’s by iMessage language message may go away empty-handed. An obscure iPhone bug can ensure that some audion messages remain completely hidden from the recipient. At the same time, the broadcaster receives no indication that his message has not arrived. The bug has on this bizarre Podcast Search Engine made aware of the recent episodeafter listeners pointed out the problem.

The sticking point is the ET sign

Ben & Jerry’s did not end up on a blocking list, but all iMessage audion news seems to be lost in which a product name or manufacturer is mentioned with a commercial and sign (ET sign). There are several well -known candidates in the United States – from arms manufacturer Smith & Wesson to the bookseller Barnes & Noble to the Dave & Buster catering chain. In Europe, Villeroy & Boch falls, for many other companies this is only used in the long form, which is probably rarely mentioned in voice messages.

The error obviously occurs entirely on the recipient’s iPhone: The voice message is received properly there, but is not shown. Mac & i could also reproduce the behavior on one device – at least sometimes.

The problem is apparently that Apple’s automatic transcription of the voice message inserts an ET sign into the text, but without masking this correctly for HTML/XHTML. As soon as Apple’s “Messagesblastdoorservice” tries to parse the transcript, there is a mistake because only there & and not & stands, As can be seen from an analysis by the developer Guilherme Rambo.

Apple’s pedantic “Blast Door”

“Blast Door” is a protective function integrated by Apple, which is intended to make targeted spyware attacks more difficult. The anti-spyware system then breaks off the process, the audion notification is therefore not shown and remains hidden from the recipient.

Ultimately, Rambo notes that Blast Door is working correctly, after all, the protection system is designed to not even display incorrectly formatted messages. Bad parser would probably accept the incorrectly formatted XHTML anyway, the developer writes – especially such “forgiveness when processing data formats”, leads to security problems. When Apple in the transcription of such brand names with a commercial and re -improvement remains open for the time being, in iOS 18.5 the bug still seems to exist.