nfc

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

Here is my write NDEF message code: let readerWriter = NFCReaderWriter.sharedInstance() let payloadData = NFCNDEFPayload(format: .nfcWellKnown, type: U.data(using: .utf8)!, identifier: Data(), payload: google.com.data(using: .utf8)!) let message = NFCNDEFMessage(records: [payloadData]) readerWriter.write(message, to: tags.first!) { (error) in if let err = error { print(ERR:(err)) } else { print(write success) } self.readerWriter.end() } First Issue: When I want to read the NFC chip in the background without opening the app, I find the detection speed is not ideal. For example, this code writes google.com this time. When performing background reading, it does not successfully read every time the chip is near, and there seems to be a one-minute interval. Second Issue: When I implemented this method in the AppDelegate: - (BOOL)application:(UIApplication *)application continueUserActivity:(nonnull NSUserActivity *)userActivity restorationHandler:(nonnull void (^)(NSArray> * _Nullable))restorationHandl

Hi, I am integrating the HCE-based API into our SDK. Ideal flow It is bit tricky to support card change (step 3 below) after field-detect/double click due to NFC action sheet. Ideally, the flow is: User double-click. App launch Hold near Reader NFC instruction (optional) User change card User tap device to POS reader payment succeed. Approach A If I follow the code snippet in CardSession, where it calls startEmulation after readerDetected, I could change card before that. However, the Hold near Reader NFC instruction is shown very late, during tap. User double-click App launch (optional)User change card User tap device to POS reader Hold near Reader NFC instruction payment succeed. Approach B If I call startEmulation after sessionStarted, I could show Hold near Reader NFC. However, I could not provide the optional capability to change card anymore. User double-click App launch Hold near Reader NFC instruction User tap device to POS reader payment succeed.

Is there a way to access the Core NFC Framework from within a watchOS app?

My app is live on the App Store, A Repeatable List, yet when the QR code is scanned, an App Clip card appears (with the correct image) and App Clip Unavailable text appears. To see this happening, scan the following QR code on an iOS 14 device: https://www.atrinh. com/qr.png (remove the spaces) A bug report has been raised: FB8711782 It is worth noting that: The website is: https://www.atrinh. com/list/index.html The banner on the website for the App Clip does not appear Tapping the NFC code to the website also shows App Clip Unavailable Sending an iMessage to someone appears as an ordinary link instead of an App Clip display Signing out of iCloud in settings seems to fix the issue, however signing back in and restarting the device causes the issue again To see working App Clips, try the following URLs: https://unwind. to https://chibi. app https://getcardpointers. com It appears that I am not the only one experiencing this issue: https://developer.apple.com/forums/thread/660410