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.

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!

Hi everyone, I am facing an issue while configuring an App Clip in App Store Connect, and I am unable to proceed due to a UI crash. Issue When I navigate to the App Clip section under my app version and click on the Subtitle field, the page immediately shows: “We can't process your request.” I am unable to enter any metadata for the App Clip experience. Console Error Previously, I observed the following error in the browser console: TypeError: Cannot read properties of undefined (reading 'appClipDefaultExperience.id')

A few months ago I tested App Clips with my app, but I don't plan to add them for now. The problem is that now I can't select a build in App Store Connect that does not contain an App Clip, and I receive the following error: "An error has occurred. Try again later." I've inspected the HTTP response to get more information about the error, and I got this: { "errors" : [ { "id" : "xxxxxxxxxxxxxxxxxxxxxxxx", "status" : "409", "code" : "ENTITY_ERROR.RELATIONSHIP.UNKNOWN", "title" : "The provided entity includes an unknown relationship", "detail" : "'appClipDefaultExperiences' is not a relationship on the resource 'appStoreVersions'", "source" : { "pointer" : "/data/relationships/appClipDefaultExperiences" } } ] } Does anybody know how to completely disable App Clips for one app without having to generate a new identifier? Thank you so much and have a great day/night! Aniol.

Hi everyone, We’re running into a serious issue with App Clip Experience updates not propagating to devices, and I’m hoping someone here has encountered (or solved) this before. Problem Once an App Clip Experience is created and used on devices, subsequent updates made in App Store Connect do not reflect on any devices, even after a long period of time. We’ve tried: • Updating the App Clip Experience URL (adding utm parameters, for example, utm_source and scanning via QR code) • Modifying Experience metadata/content • Waiting several days (over a week) • Testing on multiple devices (including devices that never opened the App Clip before) Despite this, the App Clip continues to show the initially created content, while App Store Connect clearly shows the updated configuration. Important Details • We currently have ~1,300 App Clip Experiences created • All App Clips use the same App Clip Bundle ID • The content behind the URLs updates correctly on the website • Only the App Clip continues to show stale / initial data • Removing and re-invoking the App Clip on devices does not consistently fix the issue At this point, manual updates via App Store Connect appear to be completely ignored once the App Clip is “established.” Questions 1. Is there a known hard cache or CDN behavior on Apple’s side that prevents App Clip Experience updates from propagating? 2. Is there any way to invalidate or refresh an existing App Clip Experience? 3. Does having a large number of App Clip Experiences (~1300) affect update behavior or caching? 4. Is the recommended approach to treat App Clip Experience as immutable and handle all updates via backend / dynamic content only? Right now it feels like: App Clip Experience is effectively a one-time snapshot and not a live-updatable configuration. Any insights, confirmations, or official guidance would be greatly appreciated. Thanks in advance.

Using an App Clip link encoded into a QR Code shows an error when scanning the encoded QR Code on an iPhone or iPad. After being scanned, the App Clip's banner is visible, but a message says: "App Clip Unavailable". Accessing the same App Clip URL via Safari works as expected. I've filed a feedback with more details and screenshots of the issue here: FB17891015 Thanks!

Hi, As a company, we have several apps in the AppStore that contain AppClips. With the latest iOS18 it works without any problems. With all iOS26 betas so far, however, there is always the problem “ASDErrorDomain- Error 507” and the AppClip cannot be opened. You can easily test this by scanning the following QR code with the system camera: You only ever get this error instead of the option to open the AppClip. As the iOS26 beta phase is already at an advanced stage, we are naturally concerned as to whether the problem will be solved.

We're building a UGC AR app and are leveraging App Clips to distribute AR experiences without app download. Since earlier this week, many of our users are reporting sharing experiences as App Clip doesn't work anymore. They are getting the message "AppClip unavailable" on a little card. We attached a QR code to try it yourself and a link to a different experience. We tried with multiple experiences and on multiple devices already. https://scenery.app/experience/1C925FDE-E49A-489B-BA14-58A4E532E645 Interestingly, we can't pinpoint the issue to an exact device or OS. We tested on many devices and on most, the AppClip is being displayed as unavailable, stating "App Clip unavailable", whereas it works on a few. It all worked fine last week (before September 12th). iPhone 13 Pro Max, iOS26: works iPhone SE, iOS 17: works iPhone 16 Pro, iOS 26: doesn't work iPhone 12 Pro Max, iOS 26: doesn't work iPhone 12 mini, iOS 18: does not work iPad 9th gen, iOS 26: doesn't work Please help. Our users are very dissatisfied as they expect this to work and it's a crucial feature. We already filed a radar via Feedback assistant: FB20303890

Hei! I'm currently running into an issue that I cannot create App Clip Invocations for a build in Appstore Connect. Tested with Safari, Chrome and Firefox. Also with a Windows machine. I select the build from TestFlight view I click "Add App Clip Invocation" I fill the data in the modal I click "Add" Nothing happens and I don't see any errors in the logs in developer tools with the browsers.

We are currently implementing App Clips in our app. While we have carefully optimized the App Clip size to keep it lightweight (~3.69MB), we have noticed that on the first load, displaying the App Clip Card and activating the “Open” button takes a surprisingly long time (approximately 2–3 seconds). Subsequent loads appear to perform normally. We understand that this behavior may not be directly controllable from the app development side, but we would like to know if there are any possible ways to improve it. Minimizing the time it takes for users to access the content is extremely important, as delays on the first interaction can negatively impact the user experience. Any guidance or best practices to make the App Clip Card and its “Open” button respond faster on first load would be greatly appreciated.

Issue with App Clip Card Showing "App Clip unavailable" for DIGI LIVE App In my DIGI LIVE application, I have an App Clip configured for iOS 17.6+ (the file exceeds the 15 MB limit), and I have made all the necessary preparations for the App Clip to work correctly. However, the App Clip card constantly displays an "App Clip unavailable" error for various users (depending on their system language). The URL associated with the App Clip invocation is: https://ar.digi-live.de The AASA file is located at /.well-known/apple-app-site-association and contains the required fields for the App Clip: { "applinks": { "details": [ { "appIDs": ["N9QR6LF765.de.digilive.app"], "components":[ { "#": "no_universal_links", "exclude": true, "comment": "Matches any URL whose fragment equals no_universal_links and instructs the system not to open it as a universal link" }, { "/": "*", "comment": "Matches any URL like ar.digi-live.de" } ] } ] }, "appclips": { "apps": ["N9QR6LF765.de.digilive.app.Clip"] } } If I use the default App Clip link (https://appclip.apple.com/id?p=de.digilive.app.Clip) to launch it, the "App Clip unavailable" error no longer appears. But if I delete the App Clip from the settings, the error comes back, and it can only be launched again using the default link. It feels like the problem is with the App Clip loading at the moment the App Clip card is triggered — it simply fails to load. Video https://storage.yandexcloud.net/mmrs/files/digilive/IMG_2259.mp4

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,

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 have an app clip installed via TestFlight. My AASA file is configured correctly (per 'Domain Status' in TestFlight). I want to be able to run the app clip flow (app clip card showing and app clip card launched) by invoking UIApplication.shared.open(url) from a different app, or by pressing the URL from notes app. This doesn't seem to work. The only thing I am able to do is run the flow when scanning a proper QR code after configuring Local Experience with the matching parameters. But as stated above, the flow will not work when invoking the URL from a different app. Is the proper way to fix this is to define an HTML page for that URL path that contain the element with app-clip-bundle-id attribute that will match the Local Experience configuration? Is there another way to make this flow work with TestFlight releases? what are my options?

For a few days now, we are getting an error page saying "403 Forbidden" when clicking the "Edit Advanced Experience" button for our App in App Store Connect. Also, the cache status for our domains says "Cache status updated on Feb 29, 2024 at 10:49 AM." which is almost a week ago. Are we the only app having this issue, or is it more widespread?

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

Hello, I've correctly configured my Apple App Site Association. Running a curl command returns: $ curl -L -i https://example.com/.well-known/apple-app-site-association HTTP/2 200 accept-ranges: bytes access-control-allow-origin: * cache-control: public, max-age=0, must-revalidate content-disposition: inline content-type: application/json date: [DATE] etag: "[ETAG]" server: Vercel service-worker-allowed: / strict-transport-security: max-age=63072000 x-matched-path: /api/apple-app-site-association x-vercel-cache: HIT x-vercel-id: [VERCEL_ID] content-length: 250 {"applinks":{"details":[{"appIDs":["<TEAM_ID>.<APP_BUNDLE>"],"paths":["/game/*"],"components":[{"/":"/game/*"}]}]},"appclips":{"apps":["<TEAM_ID>.<APP_CLIP_BUNDLE>"]},"webcredentials":{"apps":["<TEAM_ID>.<APP_BUNDLE>"]}} Additionally, inspecting the experiences JSON in App Store Connect's Advanced Experiences for App Clips shows: { "count": 1, "from": 0, "size": 50, "hits": [ { "bundleId": "<APP_CLIP_BUNDLE>", "heroImage": "https://is5-ssl.mzstatic.com/image/thumb/[IMAGE_TEMPLATE]", "createDate": [TIMESTAMP], "orgId": "[ORG_ID]", "subversion": [SUBVERSION_TIMESTAMP], "contents": [ { "default": true, "subtitle": "Tap open to view", "language": "en", "title": "Multi" } ], "version": [VERSION_TIMESTAMP], "adamId": "[ADAM_ID]", "id": "[EXPERIENCE_ID]", "status": "PUBLISHED", "link": "https://example.com/game", "appTag": { "appTagUrlEncoderVersion": "version0", "appTagSvgEncoderVersion": "0", "appTagId": "[APP_TAG_ID]" }, "modifiedBy": "[MODIFIED_BY]", "action": "OPEN", "isPoweredBy": false } ], "aggs": { "appTags": { "buckets": { "*": { "doc_count": 1 }, "null": { "doc_count": 0 } } }, "bundleIds": { "buckets": [ { "key": "<APP_CLIP_BUNDLE>", "doc_count": 1 } ] }, "statuses": { "buckets": [ { "key": "PUBLISHED", "doc_count": 1 } ] }, "hosts": { "buckets": [ { "key": "example.com", "doc_count": 1 } ] }, "actions": { "buckets": [ { "key": "OPEN", "doc_count": 1, "categories": { "buckets": [ { "key": "N/A", "doc_count": 1 } ] } } ] }, "vendorPlaceStatuses": { "buckets": [] } } } So it appears to be published, despite what the UI indicates. However, I still cannot invoke my App Clip via the universal link. The desired behavior is to invoke it from iMessage. Has anyone encountered this issue or have suggestions on how to resolve it?

I really need help guys:/ All works when testing, but not on production:/ Main app and its app clip is released. Here is the app: https://apps.apple.com/pl/app/ar-city-your-ar-experience/id6745802339 Here is the associated apple-app-site-association: https://arcity.ai/.well-known/apple-app-site-association and its content: HTTP/2 200 accept-ranges: bytes access-control-allow-origin: * age: 0 cache-control: public,max-age=86400 cache-status: "Netlify Edge"; fwd=miss content-type: application/json date: Wed, 28 May 2025 14:35:03 GMT etag: "59e807a4581e56f56ed0029251edda98-ssl" server: Netlify strict-transport-security: max-age=31536000 x-content-type-options: nosniff x-nf-request-id: 01JWBN2WHPEK443GB2VTZEWDGW content-length: 677 { "applinks": { "details": [ { "appIDs": ["TANE496532.com.arcity.app"], "components": [ { "#": "no_universal_links", "exclude": true, "comment": "Exclude links with this fragment." }, { "/": "/ar/*", "comment": "Matches any path under /ar/ for AR experiences." }, { "/": "/", "comment": "Match root path with optional query parameters." } ] } ] }, "webcredentials": { "apps": ["TANE496532.com.arcity.app"] }, "appclips": { "apps": ["TANE496532.com.arcity.app.clip"] } }% Here are metadata: Domain status: I added (obviously) default app clip experience, but also advanced app clip (which should be not needed as on iOS >16.4 default one should supports QR code scanning): When I check on my device under Settings -> Developer -> APP CLIPS TESTING -> check for "https://arcity.ai" I can see (that worries me:/): Launching app clip from smart banners works (you can check that by opening arcity.ai on your device), but scanning QR codes (with system camera) don't:/ It just opens Safari. Any thought appreciated.

Hey everyone, I’ve got a weird App Clip issue that I’m hoping someone can shed light on. Here’s what’s going on: ✅ When I type or tap https://adagxr.com/card/ar4 in Safari, the App Clip card shows up immediately, and the clip launches fine. ❌ When I scan a QR code with that exact same URL (confirmed it’s fully https:// and no redirects), the camera banner shows, I tap it, Safari opens the page, but the App Clip card never appears. Some details: Clip bundle ID: C7XA5GZG35.Effectization-Studio.Effectization-Instant.Clip Clip size: 1.17 MB (way below the 15 MB limit) Domain: adagxr.com, fully secured with Let’s Encrypt TLS cert AASA file: hosted at https://adagxr.com/.well-known/apple-app-site-association AASA config: includes both applinks and appclips entries Devices tested: iPhone 14 Pro (iOS 17.5.1), iPhone 12 mini (iOS 16.7.8) Other App Clips: launch just fine via QR codes on these same devices What I’ve already checked: Confirmed the QR code has the same HTTPS URL. Cleared Safari cache, rebooted devices, and tested on fresh devices that hadn’t seen this QR before. Checked that the TLS certificate is valid and trusted (padlock shows secure). The default App Clip experience in App Store Connect is published and showing. Main question: Does QR-based invocation require an Advanced App Clip Experience in App Store Connect, even if the default experience already works in Safari? Any ideas on why Safari works perfectly, but QR triggers don’t surface the App Clip card? Would love to hear if anyone else has seen this or has tips for debugging. Thanks!

We have an iOS App built in .NET MAUI (Multi-platform App UI). This is a web view App. We wish to integrate APP Clips into this App. But we are unable to do it, due to less available resources online on such implementation. We do not wish to share code between .NET MAUI App and App clips We understand it is not possible to add APP Clips without a parent swift/Xcode app. As an alternative solution we were thinking to Create a new APP in APP Store Connect using XCode/swift and integrate app clips to it. This parent app when downloaded by users will only redirect users to our MAIN .NET MAUI app to app store connect. We need to know if such apps will be approved by APPSTORE Connect? Please guide us on this Also please do let us know if you have any other solution to integrate App clips to a .NET MAUI App