International Domain Names allows non ascii character of non English languages in domaine name and then in email addresses. For many years IDN were correctly handled both on MacOS and iOS. This is no longer the case. iOS Another poster already reported on this forum that IOS mail is no longer able to send mail from an IDN email address, always displaying an incorrect message about an "invalid address". This poster only had general incompetent advice from an Apple poster about checking his email account configuration. As this poster already reported an IDN account with worked previously no longer does. I can't date precisely which release of iOS regressed. iOS 15 for sure, 14 possibly. MacOS Since yesterday, I spend time trying to figure out why my S/MIME certificate no longer worked on my Mac, for the same IDN email account. After many test I figured out a partial workaround : the S/MIME certificate is setup with the punnycode form of the IDN domain adding an identity preference for the certificate did no help but editing this identity preference by changing the punnycode form to the utf (accented) form did help : the Mail app is now able to sign outgoing email. I find no way to restore the ability to encrypt email for this account neither replying to another account for which I have another certificate, nor sending encrypted mail to the IDN address from that other account. Clearly on both iOS and MacOS there is a regression in the punnycode/utf translation/comparison. That may be due to the utf8/utf16 conundrum or normalization forms NFC/NFD. I posted also on the Apple users discussion forum but though more Apple competence are here, so I maximize the chance for this issue to be resolved.

A few customers are experiencing this :They make a purchase on a non consumable item.The purchase apparently process normalyThe device trigger a paymentQueue:updatedTransactions: in the observer, that we send to our server to register a pending transaction. The transaction is acknowledged (finishTransaction:)Then the device pick-up the application receipt and send it to our server for further processing.This receipt has no IAP in the array.Restoring purchase triggers again a new transaction, receipt is not updated eitherThe receipt eventually got updated, sometime a few minutes, hours or even 3 days later.We monitor this because customer contact our support. So we are able to manually activate the purchase, asking them to restore transaction some time later just for a checking purpose. So at some point we receive a valid application receipt to consolidate our server side purchase database.We have about ten years experience with IAP on iOS. Our Mac companion application launched a few months ago and most purchases process as they should.We suspected a payment issue. Recently a customer reported that the payment was dated on the day or purchase, while the receipt came 3 days later. So we have no clue beside some kind of inconsistency on Apple servers. So payement should not be involved.Related or not we logged some rare errors while validating receipt :Receipt: {"status":21199, "environment":"Production", "is_retryable":true, "exception":"com.apple.jingle.commercelogic.inappcache.MZInAppCacheAccessException"}There have been other thread about the application receipt not being updated. Mainly involving auto-renewable subscription. Before postin a bug report, I'd like to know if this is a known issue