Hey there,
We've been using App Store Connect API to manage (create/update) Advanced App Clip Experiences via App Store Connect API.
Everything has worked fine, we've been able to successfully manage hundreds of app clips but all of a sudden starting on December 15th the API started returning the following error:
"id" => "1e15b36b-5347-4af0-9bab-7f6626ffec65"
"status" => "409"
"code" => "ENTITY_ERROR.INCLUDED.INVALID_ID"
"title" => "The provided entity id is invalid"
"detail" => "The provided included entity id 'EN' has invalid format"
"source" => array:1 [▼
"pointer" => "/included/0/id"
]
It does seem to be an API bug considering it has always worked fine and we didn't change anything on our side, the /included/0/id value has always been EN and never changed.
Moreover, EN still seems to be a valid value according to the API docs and there are no changes reported of that field in the API release notes.
Here's the request ID: 1e15b36b-5347-4af0-9bab-7f6626ffec65
I've tried using different values through trial and error (en, EN, EN-US, ...) and none of them worked.
App Clips
RSS for tagProvide a way to quickly access and experience what your app has to offer. An app clip is a small part of your app that lets users start and finish an experience in seconds, even before downloading your app.
Posts under App Clips tag
114 Posts
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I’m configuring App Clip launch behavior and would appreciate some clarification.
In my setup, the App Clip launch URL is the same as the deep link used to open the full app. Both are configured in the Apple App Site Association (AASA) file.
Observed behavior:
Scanning a QR code with this URL correctly launches the App Clip.
Tapping the same URL when it’s shared (for example, via Messages) launches the full app via the deep link instead of the App Clip experience.
I’m reviewing the documentation here:
https://developer.apple.com/documentation/appclip/configuring-the-launch-experience-of-your-app-clip#Choose-App-Clip-experiences-you-want-to-support
The table mentions that an App Clip can be invoked via “A shared link to an App Clip in the Messages app.” However, when I tap the shared link in Messages, the deep link experience is triggered instead of the App Clip.
My questions are:
Is this behavior expected when the App Clip URL and the app’s deep link URL are the same?
Does launching an App Clip from a shared Messages link require a distinct URL or additional configuration beyond what’s in the AASA file?
Are there specific constraints or priorities between universal links for the full app and App Clip invocation in this scenario?
Any clarification or guidance would be greatly appreciated.
Thank you.
Hi everyone,
I’ve completely removed my App Clip:
Deleted all Advanced App Clip Experiences
Removed the App Clip target from my build
Removed App Clip references from my apple-app-site-association file
Deleted the meta tag from my website:
However:
When scanning the QR code, the App Clip card still appears with:
"This App Clip is not currently available in your country or region."
This link still works for my App Clip, which is not what I expected:
https://appclip.apple.com/id?p=com.example.appclip
Does anyone know why the App Clip card is still showing and how to fully remove it?
Thanks!
I published my app clip last year in the App Store.
I can successfully open my app clip in iMessage or via link URL. but scanning the QR code of the very same URL leads to the "app clip is unavailable" error, in this case, I can see my application name and banner correctly.
Any Idea why?
Hi everyone,
I’ve removed my App Clip completely:
Deleted all Advanced App Clip Experiences
Removed the App Clip target from my build
Removed App Clip references from my apple-app-site-association file
Deleted the meta tag from my website:
But when I scan the QR code, the App Clip card still appears with:
"This App Clip is not currently available in your country or region."
Does anyone know why this is still showing and how to fully remove it? we need to show our website when this QRCode is scanned.
Thanks!
I am requesting assistance with an issue involving my Advanced App Clip Experience, which has remained in the “Received” state for more than few months, preventing the App Clip from becoming available when invoked via QR code.
App Details
App Name: Yellow Label Verification
App Store Bundle ID: com.acviss.demoindia
App Clip Bundle ID: com.acviss.demoindia.Clip
Team ID: F2RLQ4VV59
App Version (Live): 1.4
Domain: acviss.com
Issue Summary
My Advanced App Clip Experience is stuck in the “Received” status. The “Publish” and “Build Assignment” options never appear, even though:
The updated AASA file is correctly published at:
https://acviss.com/.well-known/apple-app-site-association
It contains the correct appclips → appID and paths entries
It is served with the correct application/json content type
Domain validation in App Store Connect shows Validated
The App Clip build is already approved and live on the App Store
Safari-based App Clip invocation works as expected
Despite this, the Advanced App Clip Experience has not transitioned from “Received” to “Processing” or “Published.”
Because of this, QR-based invocation consistently shows “App Clip Unavailable”, indicating that the App Clip Experience has not yet been activated on Apple’s backend.
Reproduction Steps
Publish correct AASA file with appclips array and paths
Validate domain (shows green “Validated” in App Store Connect)
Open the Advanced App Clip Experience in App Store Connect
Status stays as Received
“Build Assignment” or “Publish” buttons never appear
QR scanning of the App Clip URL continues to show App Clip Unavailable
Request
Could you please check the backend processing of my App Clip Experience and manually trigger the sync or processing
It appears that the App Clip Experience is not being processed even though all configuration, AASA, and domain validations are correct. I would greatly appreciate your assistance in resolving this so the App Clip can be invoked successfully via QR.
Thank you very much for your help and support.
We have an app with a few App Clip Advanced Experiences. Since around 28th of August the status of the experiences seems to be stuck in either CREATE_SUBMITTED or UPDATE_SUBMITTED and they don't get updated to PUBLISHED anymore.
I found this in the experiences JSON loaded by AppStoreConnect when editing the experiences:
"statuses": {
"doc_count_error_upper_bound": 0,
"sum_other_doc_count": 0,
"buckets": [
{
"key": "PUBLISHED",
"doc_count": 182
},
{
"key": "CREATE_SUBMITTED",
"doc_count": 7
},
{
"key": "UPDATE_SUBMITTED",
"doc_count": 3
}
]
},
This shows that 10 experiences are stuck in other status than PUBLISHED.
I created a Feedback with ID FB15041208 and a DTS last week.
This is REALLY important for us to be fixed immediately since we have customers that rely on this!
When updating an existing advanced app clip experience, the change doesn't actually apply. It shows the correct image in the UI, but when you use the app clip it shows the old image. Looking into it more, the status has "UPDATE_SUBMITTED". Seems related to this issue (https://developer.apple.com/forums/thread/810544) and this issue (https://developer.apple.com/forums/thread/810351).
Hello,
We are reporting an issue with an Advanced App Clip Experience that we created in App Store Connect.
Issue: The Advanced App Clip Experience, created on Wednesday, December 10th, has remained in the 'Received' status since its submission, and we have not seen any progress or change in its review status.
Context:
After conducting extensive research through the Apple Developer Forums, we have observed that numerous developers have reported similar problems with Advanced App Clip Experiences getting stuck indefinitely in the 'Received' status. In several of these discussions, the recommended course of action for persistent delays or lack of status updates is to open a report via Feedback Assistant.
FYI, our feedback assistant number is FB21344257
We kindly request your assistance in investigating this matter and helping us move forward with our Advanced App Clip Experience.
Thank you for your time and support.
Best regards,
The title says by itself.
We've been using advanced app clips a lot and have created more than hundreds of advanced app clips for the customers.
Suddenly, few days ago, the most recently created advanced app clips stopped working as they got stuck with CREATE_SUBMITTED status.
It seems like it has already happened before to someone else: https://developer.apple.com/forums/thread/763374
It probably be OK if it showed a Safari notification but it shows an error due to another bug reported here: https://developer.apple.com/forums/thread/803187
Hello,
We are encountering an issue where invoking our App Clip via a Safari Smart App Banner fails on certain devices, particularly those running iOS 26.
When a user taps "Open" on the Smart App Banner, the App Clip card attempts to load but ultimately fails with ASDErrorDomain Error 507.
The error occurs consistently on specific devices, while other devices function correctly. In some instances, the App Clip card metadata/UI appears momentarily (flashes on the screen) before the error message is displayed and the process terminates.
Has anyone else experienced this specific ASDErrorDomain error? We have already submitted a report via Feedback Assistant, but any insights or workarounds from the community would be appreciated.
Thanks!
I recently submitted an Advanced App Clip Experience, and the status currently shows as "Received."
My default App Clip Experience is already working well, but I need the advanced experience to go live as soon as possible. Does anyone know the typical timeframe for this to be published?
Also, will the status change from "Received" to something else when it is fully active? Any insight would be appreciated.
Thanks!
We are enrolling on behalf of an organization. We do have following information with us.
• Legal binding authority,
• Legal entity status,
• A D-U-N-S® number, and
• A website.
We are always getting the message as :-
There may be an issue with your account that needs to be resolved before you can continue. Please contact support.
This seems very generic message we are not getting the reason why we are not able to enroll for apple dev program.
Topic:
Developer Tools & Services
SubTopic:
Apple Developer Program
Tags:
App Clips
Xcode
Feedback Assistant
Developer Program
Hello!
We are having issues in production where users are shown the app clip banner with an error state after releasing an app where removed the app clip.
We deactivated all advanced experiences.
We created a new build where app clip has been disabled (Shows in appstore connect that we dont have app clip)
Released the build to production.
We are getting complaints from customers that they are getting a banner, but the banner shows app clip is unavailable.
Any recommendations or suggestions?
Hello Apple Developer Forum Community,
I’ve got a problem with the signing process of my AppClip Test App. Can someone help me? As I don’t know hot to get the certificate...
Hi
Is there a way to create a dynamic app clip card experience? I have advanced app clip experiences set up and working fine already and but I am looking to provider a more dynamic experience.
For example, my invocation url now is https://mycompany.com/profile/<profile_slug>, this URL shows the app clip card with the title, subheading, and cover image as configured in app store connect which is right. But I would like to show a different title, subheading, and cover image based on the <profile_slug> in the invocation URL. Like we can show the name as the title, job title as the subheading, and profile's banner image as the cover image for the app clip
It seems like this is possible as I have seen one company do this for their product. Apple has no mention for such a thing in their documentation from what I have seen.
Any help would be appreciated.
Thanks
Hi everyone,
We’re experiencing a persistent issue with an App Clip Experience that continues to load on iOS devices even after being deactivated in App Store Connect more than 48 hours ago.
Issue Summary
An App Clip Experience tied to the URL pattern
https://srgplus.com/u/...
keeps appearing when scanning NFC tags or QR codes, despite being removed from App Store Connect.
Key Details
The App Clip Experience was deactivated over 48 hours ago.
iOS still launches the App Clip when scanning NFC tags or QR codes that match the URL structure.
The specific token-based App Clip Experience (for example: https://srgplus.com/u/iohgqa) was removed, but iOS still loads an App Clip as if the Experience exists.
It seems like iOS is falling back to a previously registered base URL Pattern such as:
https://srgplus.com/u
or possibly even https://srgplus.com
The problem:
This fallback App Clip is not visible anywhere in App Store Connect → Advanced App Clip Experiences.
So we cannot delete or modify it.
The behavior persists across:
Multiple devices
Different networks
After clearing device caches
After reinstalling our app
Even after scanning using devices that never used this App Clip before
This makes us believe that the App Clip Experience may be:
Cached on Apple’s servers
Or orphaned/hidden in App Store Connect
Or not properly removed from the URL pattern registry
Steps to Reproduce
Deactivate an App Clip Experience in App Store Connect.
Wait 48 hours or more.
Scan an NFC tag or QR code pointing to a previously used URL pattern.
App Clip still appears, even though no active Experience exists.
Expected Behavior
App Clip should stop appearing once the Experience is deactivated and removed.
Actual Behavior
App Clip continues to load indefinitely, suggesting a cached or orphaned configuration.
Question
Has anyone encountered similar behavior?
Is there a way to request a manual purge of App Clip URL patterns or cached Experiences from Apple’s side?
Any guidance or insights would be greatly appreciated.
Thank you!
Dear Apple Developer Support,
I am writing to seek guidance regarding App Clips launch source differentiation in our restaurant application.
Background:
Our restaurant uses QR codes that are permanently associated with specific table numbers. These QR codes successfully launch our App Clip and pass the table information via NSUserActivity with NSUserActivityTypeBrowsingWeb.
Current Issue:
We are facing a significant challenge in distinguishing between different launch sources:
Camera Scan/URL Launch: When customers scan the QR code using the native camera or tap a URL, the App Clip launches with the correct table information.
App Library Launch: When customers launch the App Clip from the App Library, it restores the previous NSUserActivity with potentially outdated table information.
The Problem:
Since we cannot determine whether the App Clip was launched from the camera/URL or from the App Library, we cannot reliably decide whether to use the table information carried by userActivity. This causes customers to be directed to incorrect tables when launching from the App Library.
What We've Tried:
We have attempted various approaches to differentiate the launch source:
Checking for AppClipActivationPayload - but it exists in both scenarios
Examining UIApplicationLaunchOptionsKey and UISceneConnectionOptions
Analyzing URL parameters and timestamps
Implementing custom state management
However, none of these methods provide reliable differentiation between camera scan launches and App Library restorations.
Question:
Is there any official API or recommended approach to programmatically determine if an App Clip was launched:
From a camera scan/URL tap (fresh launch), OR
From the App Library (state restoration)
Any guidance on how to properly handle this scenario would be greatly appreciated, as it significantly impacts the user experience in our restaurant ordering system.
Thank you for your time and assistance.
Best regards
Struggling to find a solution. App is approved but when I make an advanced experience it stays in the received status forever. If I try to tap the nfc chip, instead it says to open in safari at the top. I do that and there is an app clip banner at the top that says view and when I hit that the app clip shows. Otherwise I've tried everything I can to get this working. Please help
Unexpected behavior encountered when scanning NFC tags.
Imagine a link shortener web service where users can create lots of different URLs that are hosted on the same domain eg, https://short.com/unique-path
The service has optional App Clip capability -- users can select any of their links and have the service create an App Clip for the selected link(s).
Users can encode their URLs into NFC tags and have their customers scan NFC tags.
Let's take just two URLs for example:
https://short.com/foo
https://short.com/bar
The /foo link does have an App Clip associated with it while /bar does not have it. Each link has been encoded into appropriate NFC tag.
Expected behavior when scanning from an iPhone:
/foo -- shows an App Clip popup.
/bar -- shows a "Open in Safari" default notification.
What's actually happening
/foo -- opens App Clip poput with correct metadata (title, subtitle, image) which is totally expected behavior.
/bar (the one that doesn't have app clip associated with it) -- opens an App-Clip-like popup with the following error: CPSErrorDomainError 2 (see attachment below)
So for some reason when someone scans an NFC tag with a URL that is not an App Clip and never has been -- it always shows that error regardless whether the URL exists or does not exist. I've tried few different/random URLs (which don't have an App Clip associated with it) and all of them show the same error.
Additional details:
All links use the same domain and URL format: domain.com/path where path is a short string of random a-Z characters.
All App Clips are created at the same iOS app.
AASA is good: Cache and Debug -- both green.
This issue has happened to lots of users on lots of different iPhones and iOS'.
Since the issue's been happening to lots of different users on different iPhone(s)/iOS' no sysdiagnose is attached. Actually it works the same on every device/iOS we've tried.
Before submitting the issue, I've found few other developers reporting the same issue.
What's interesting though is none of the links I've went through comes with a definite answer and it seems like this issue just randomly comes and goes without any specific changes on the server and/or iOS app.
Dropping the links of similar issues below.
https://developer.apple.com/forums/thread/671433
https://developer.apple.com/forums/thread/665969
https://developer.apple.com/forums/thread/775316
https://developer.apple.com/forums/thread/764545