I had the same issue and spent lots of time figuring it out. Here's what currently works for me: // data field data.relationships.localizations.data.0.id = 'EN' data.relationships.localizations.data.0.type = 'appClipAdvancedExperienceLocalizations' // included field included.0.id = 'EN' included.0.type = 'appClipAdvancedExperienceLocalizations' included.0.attributes.title = String included.0.attributes.subtitle = String included.0.attributes.language = EN

Any updates @natebrierhinge?

Any updates @Madiska ?

@Arxos have you had any issues with Apple creating placeholder experiences? This seems to be a good workaround but still I wonder what would Apple do if they detected this behavior.

I'm going to add more details here: I've clicked "Clear Experience Cache" countless times. Here's what Settings -> Developer -> App Clips Testing -> Diagnostics show for two URLs that are on the same domain but with different path (a.k.a /foo /bar at the example in the original post): This is diagnostics data of the URL that does have an App Clip associated: https://short.com/foo This is diagnostics data of the URL that does not have an App Clip associated: https://short.com/bar (Note: same domain, slightly different path)

One more use case of unexpected behavior with a new URL: /baz /baz does have an App Clip associated within App Store Connect and works fine, as expected. But whenever someone deactivates it within App Store Connect, it starts showing the same CPSErrorDomain error 2.

What's interesting is I have another iOS that uses App Clips as well but on a different domain. The App Clip settings look pretty much the same on both apps and AASA is fine on both domains as well. However, it works perfectly fine on the other app. When the URL has an App Clip associated, it shows an App Clip popup. If it does not have it, it shows default Safari notification. But on this app, it just keeps showing the CPSErrorDomain error 2 when the URL does not have App Clips associated with it or it has but it's been temporary deactivated.

Another interesting thing is when reading an NFC card that has just domain without path, it works as expected: https://short.com -- Shows "Open in Safari" notification, expected behavior since there's no App Clip with this invocation URL. https://short.com/ -- Shows "Open in Safari" notification, expected behavior since there's no App Clip with this invocation URL. https://short.com/a -- Shows the CPSErrorDomain error 2 popup. There's no App Clip Invocations registered with this URL. When checking these three URLs at Settings -> Developer -> App Clips Testing -> Diagnostics -- it shows the same information for all three URLs (it just shows the same as in the second Diagnostics screenshot I attached in replies above). *Just a reminder that short.com is just an example domain here.

More information: the app clip itself is less than 1mb.

@AxM1983 where did you get these logs? We currently experience a similar issue (https://developer.apple.com/forums/thread/803187) and hope some logs could helps us.

Here's another interesting thing that's happening. I've tried clearing experience cache (Settings -> Developer -> App Clips Testing -> Clear Experience Cache) and immediately after that scanning URLs that don't have app clips as invocation URLs. What sometimes (3 out of 10 attempts) started happening is this: Clear cache Scan NFC tag Shows "Open in Safari" notification // Expected behavior Scan NFC tag again Shows "No app clip available" Scan NFC tag again and again and again Shows "CPSError Domain error 2" All other attempts it just shows CPSErrorDomain.

Just submitted a bug report. (sysdiagnose attached) FB20563121

When scanning such URLs via QR code, it works fine and just opens these links in Safari is there's no App Clip associated with it.

Adding even more information: We've tested it with a different app where everything works as expected and we started getting the same CPSErrorDomain error 2 once we've created >50 advanced app clips. Activating/deactivating advanced app clips when registered on the domain without any path works fine and once deactivated, it will show the Safari notification.

@janenalleman I've seen it happen on iOS 18 as well.