nfc

Confirm that you are following the instructions 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 applicable limit. For

You can either implement background NFC reading to read the data from the tags to determine what video will play, and then send a notification to the user to open the app. Or you can embed a direct URL to your app and have the system put up a notification to launch your app. You cannot launch your app in the foreground to play a video without the step where the user taps on a notification of some kind.

If you implement an App Clip, then the NFC will launch your App Clip or your App (if the user installs it). But it will still need the user to tap the open button on a notification to actually launch your App or App Clip. You cannot have your app launched into the foreground with zero user interaction.

I noticed that Apple have introduce App Clips, which can use NFC to pop up my app directly.

We can't help you with what happens in the build with that podspec. Anything we say will be assumptions. As for app rejections, unfortunately, this is all hypothetical. App Review will handle each app on a case by case basis and it is not possible for anyone to say there will be an issue without knowing how the app is built, what NFC APIs are being referenced or not, and what the app is for. And also, what the rejection is for exactly. If they get a rejection, the app developers can ask for a technical review and determine what exactly is causing the rejection and how they can fix the problem.

It is probably too early for documentation and sample release. I think they will come out soon, maybe with beta 2. By the way, for what I've been able to understand, the new eventTicket format is an NFC only, so I think you'll need to provide NFC data for it to show up.

We have added CoreNFC as a weak_framework in our podspec s.weak_frameworks = [CoreNFC] Few clients don't use the NFC feature and few clients use it. People who use don't have any issue with it. People who don't use it, will they have an issue when their app is submitted for review ? They have not added the NFC permission in their Info.plist and have not added the capability as well. Will it still be an issue for such clients?