Yea, I'm not seeing an app clip section when I open testflight on my device, not for this app. Even though App Store Connect has it saying 4 valid domains, and I have added app clip invocation urls in testflight section.

The bug specifically is that when I manually manage signing and use a provisioning profile downloaded with the correct team id, Xcode still shows the old incorrect id - in spite of its provisioning profile.

After my breakthrough with the 4 approved domains mentioned below. I found the docs that outline clearing the experience cache. I tapped that in settings > Developer > app clips, but I’m not sure if it cleared the safari url app clip check cache, or another cache. Also there was no visual feedback to confirm the cache was cleared after I tapped it So I’m not sure it worked. Also it did not change my result. App clips are still not yet presenting.

Then I ran it on a new device to avoid any cache issues, then I created a QR code for the following: akin-server-side-staging.onrender.com/appClips/referral/venueToUser, and I think it pinged my aasa file endpoint as I have a new record of that. However it still did not go to the app clips experience. So I added the domains to the app clips target that you recommended (with the appclilps prefix), but now App Store is throwing an error for those domains: Invalid Entitlement: Unknown ID

I changed my entitlements for app clips to the following: applinks:akin-server-side-staging.onrender.com applinks:akin-server-side.onrender.com appclips:akin-server-side-staging.onrender.com appclips:akin-server-side.onrender.com appclips:akin-server-side-staging.onrender.com?mode=developer appclips:akin-server-side.onrender.com?mode=developer

I'm available for the next 40 minutes, and I will also be available at 4PM-5:30PM today, 4PM-7PM tomorrow.

sent.

Sorry I think your prior post came through at the same time as my last post. Thank you for sticking with this. Here are the entitlements for the parent target. Here are the entitlements for the app clips target:

@DTS Engineer Could you please take a peek at Apple's Codebase where this error Invalid Entitlement: Unknown ID is being thrown so we can get a sense of all the possible causes? I'm at a loss of what to try next.

No worries. This is the same JSON - which seemed/s proper to me - that my endpoint was providing before posting my question to this forum. So I am still getting Invalid Entitlement: Unknown ID in the App Store Connect dashboard for this and not surprisingly, when I open the camera app on the my testflight build and scan an app clip related QR code I created it only opens safari and doesn't show an app clip. I figured resolving this Invalid Entitlement: Unknown ID is a necessary first step.

I thought we weren’t supposed to return json for HEAD as it breaks http guidelines. Shouldn‘t we be using the get invocation (lowercase i )? curl -i -A “Albert-Bot/1.0” https://akin-server-side.onrender.com/.well-known/apple-app-site-association

Doesn’t this output indicate that the server accepted the User-Agent? It returned 200 OK with application/json. Also, for a HEAD request, is the expectation just that the headers are returned successfully, or should the AASA JSON body be returned for HEAD as well as GET?

connectedScenes is a set. I'm thrown off by the use of first. How are we certain the element returned for first is the correct scene?