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 have published the app on the App Store along with its corresponding app clip, my app clip is configured with some advanced experiences for each one of my clients, but whenever some users try to scan an NFC or QR Code they see the card rendering correctly with their configured banner image, but with the message "App Clip Unavailable". The weird thing is that both iMessage and the website to which the associated domain is set and the apple-app-site-association is stored, renders the banner or card correctly, and when the users tap the banner or card they open the advanced app clip experience correctly without any issue. I have attempted to troubleshoot the issue by checking the following: if the app clip is below 15MB if we are using a second level domain in my associated domain both for my app clip and app (excluding the www subdomain). checking if the AASA is correctly stored inside .well-known directory checking the configuration for the advanced experience I opened a case: 102233443873, and added a bunch of videos and screenshot showcasing the issue, but I have not yet received a reply

I have configured all the necessary settings for the APP Clip, but it still cannot be activated through NFC or scanning the code. What is the problem?

I have configured all the necessary settings for the APP Clip, but it still cannot be activated through NFC or scanning the code. What is the problem?

I am encountering a persistent error in App Store Connect when attempting to save URLs in the App Clip URLs section of my app version. The issue is as follows: When I enter the URL (e.g., https://4o.c.smart321.com/c/l0) and click save, I receive a 409 Conflict error with the code ENTITY_ERROR.ATTRIBUTE.TYPE. The error detail states: "does not match the uri pattern must be a valid RFC 3986 URI". The Error Log: { "errors" : [ { "id" : "9f032dd6-f456-4c90-ad9c-245c5ed041d7", "status" : "409", "code" : "ENTITY_ERROR.ATTRIBUTE.TYPE", "title" : "An attribute in the provided entity has the wrong type", "detail" : "does not match the uri pattern must be a valid RFC 3986 URI", "source" : { "pointer" : "/data/attributes/invocationUrls/1" } } ] } Conflicting Status: Interestingly, the exact same URL has already been configured under Advanced App Clip Experiences, where it currently shows a status of "Received". My AASA file is https://4o.c.smart321.com/.well-known/apple-app-site-association I have verified that the URL follows the standard HTTPS format and contains no hidden characters. Could you please clarify why the URL is being rejected in the App Version section while being accepted in the Advanced Experiences section?

Hello, I have an AppClip technical issue I'd like to ask about: Our Xiaohongshu App (Version 9.14 & Build 9140845 & appid 741292507) was submitted to the App Store for review on December 18th and approved on December 19th, starting a phased rollout. This version was the first to support AppClip functionality, and as of today the app has been fully rolled out, but I still cannot activate the Xiaohongshu App Clip Card using the NFC tag (built-in URL: https://xhslink.com/n/22UG9jlaOfv?sourceid=911). I checked all the configurations of our project's AppClip target (Associated Domains:appclips:xhslink.com), the default experience in the ASC backend (URL: https://appclip.apple.com/id?p=com.xingin.discover.Clip), and the advanced experience (URL: https://xhslink.com/n/Arxpo4IVY9X), and all showed no abnormalities. Furthermore, the default experience URL, after being written with an NFC tag, can be successfully launched by tapping the NFC tag to open the Xiaohongshu App Clip Card, and the Card can also be opened normally in Safari on the phone. However, our advanced experience URL, after being written with an NFC tag, cannot be launched by tapping the Card. Therefore, my question is: Who please can help me check why the Xiaohongshu App Clip Card cannot be launched normally using the advanced experience URL? Thank you very much! My Expectations: My advanced experience URL configured on the ASC platform, such as https://xhslink.com/n/Arxpo4IVY9X, should be recognized and validated by the iOS system when the phone is near the NFC tag and reads https://xhslink.com/n/22UG9jlaOfv?sourceid=911, ultimately triggering the App Clip Card configured in Xiaohongshu's advanced experience settings. Additionally: We have already deployed a large number of NFC tags and other materials in many online stores, and the URL (https://xhslink.com/n/Arxpo4IVY9X) is built-in, and our 9.14 version is fully implemented. However, the newly developed App Clip feature is not working, which is very urgent and I hope Apple can help me find the cause of the problem and how to improve it as soon as possible. Thank you very much!

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!

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,

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.

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