nfc

thank you for reply。 I am sure not using content-available:1 in payload with push notifications。 also our App offers NFC functionality, but it has very few users. from the log，users terminate the app and then didFinishLaunchingWithOptions was called immediately。 I think something was doing in the App, but we have not find them。 the runtime logs from the real user, and i can not reproduce it，and i will log LaunchOptions to find if if has something usefully. The phenomenon is that after the app is terminated, a cold start is immediately triggered in the background. if have more informations， thank you for sharing it.

I don't know what you mean the application has not requested background execution. As seen there you have obviously declared Remote Notifications background capability. If you are sending push notifications with the content-available:1 entry in the payload, this will have the ability to launch the app if it is not running at the time (except for if user has terminated it, then it will never launch). That is one possible explanation. Whatever it is, it is likely something you are doing in the app, and not prewarming or some other system function. I also see you are using NFC functionality. Is your app supporting background tag reading? If so, and the app is not running, then didFinishLaunchingWithOptions() will be called before application(_:continue:restorationHandler:) is called Are you not checking the UIApplication.LaunchOptionsKey in didFinishLaunchingWithOptions()? That should explain why your app is being launched. Argun Tekant /  DTS Engineer / Core Technologies

@mr_app , can you confirm you follow these recommendations from Choosing the right functionality for your App Clip: To ensure a fast launch experience, App Clips must be small:* If you make your App Clip available on devices running iOS 15 and earlier, the uncompressed App Clip binary can be up to 10 MB in size.* If you make your App Clip available on devices running iOS 16 and later, the uncompressed App Clip binary can be up to 15 MB in size. If you make your App Clip available on devices running iOS 17 and later, the uncompressed App Clip binary can be up to 50 MB in size if it meets the following conditions:* The App Clip only supports digital invocations — for example, from your website or Spotlight search — and not from physical invocations like App Clip Codes, QR codes, or NFC tags* People use your App Clip in situations where a reliable internet connection is likely, for example, at home* Your App Clip doesn’t support iOS versions prior to iOS 17 Aim to keep your App Clip well below the appli

Resolved this issue with these configuration. In the project Signing & Capabilities, add Capability Near Field Communication Tag Reading In the project Build Phases, the Link Binary With Libraries” section, add the CoreNFC.framework, and then mark it as Optional. In the project Info, add Privacy - NFC Scan Usage Description = Use NFC Do not add Near Field Communication to Required Device Capability item (this cause Incompatible hardware on iPad) Use NFC feature only if UIDevice.current.userInterfaceIdiom == .phone in program. Hope this helps, Thank you.

This sounds like it could be an issue with the system's NFC UI, and we would like you to file a bug report about this. Don't forget to include as much information as you can about the cases you see this problem with. In your case a video or images showing the distortion would be very helpful. To file a bug report, you can use the Feedback Assistant. Once you open the bug report, please post the FB number here for my reference. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Argun Tekant /  DTS Engineer / Core Technologies

While it is currently, and with iOS 18.1 would be possible for an app to emulate an NFC tag, these are reserved for very specific use cases and not available to be used for arbitrary tag emulation. You can read about the capabilities and requirements for these use cases in the following documents: NFC & SE Platform for secure contactless transactions HCE-based contactless transactions for apps in the European Economic Area (EEA) At this time, no other use cases are supported. Argun Tekant /  DTS Engineer / Core Technologies