We’re seeing unexpected NFC behavior once our app has 50+ Advanced App Clips created.
Expected:
- Scanning an NFC tag with a URL that is NOT an App Clip invocation should show the standard “Open in Safari” notification.
Actual:
- After we create ~50+ Advanced App Clips, scanning NFC tags for URLs on the same domain that are not associated with App Clips consistently shows “CPSErrorDomain error 2” instead of the Safari prompt.
- QR codes for the same non–App Clip URLs work as expected (shows Safari prompt).
- Clearing the App Clips “Experience Cache” sometimes helps briefly, but the error returns on consequent scans.
Notes:
- Domain has valid AASA. App Clip invocation URLs work as expected.
- The issue appears tied to the number of Advanced App Clips configured. Below ~50, non–App Clip NFC scans behave correctly; above that, they fail.
- Affected across multiple devices and iOS versions tested.
Repro steps:
- Configure 50+ Advanced App Clips for paths on a single domain.
- Encode a different URL on the same domain that is NOT listed as an App Clip invocation into an NFC tag.
- Scan the NFC tag on iPhone.
- Observe “CPSErrorDomain error 2” instead of the “Open in Safari” notification.
Impact: blocks our NFC use case for regular web links once we scale App Clip experiences.
Sysdiagnose #: FB20563121