We run a live App Clip used by cafes in Saudi Arabia. Customers scan a QR code at the counter to follow their order. Some customers stay on the blurred loading screen for about a minute, then get App Clip Unavailable. One cafe reported more than five cases in its first days, and I watched another happen at a cafe today, on an iPhone showing 5G with Low Power Mode on. Try Again did nothing when we tested it, and a new scan opened the clip at once. I reproduced it in 1 of 6 fresh downloads on an iPhone 17 Pro Max (build 23F84) on mobile data. The log shows: appstored starts the download from iosapps.itunes.apple.com over HTTP/1.1 on IPv6, with timeouts(60.0, 604800.0). TCP and TLS succeed and the request is sent. 71 ms later a TCP RST arrives with a stale sequence number, and the stack drops it as out of window. Retransmits go unanswered. response_bytes=0, then NSURLErrorDomain -1001 after 60.4 s. The install is cancelled, with no second attempt. A parallel HTTP/3 request finished in 414 ms, so the network was up. The clip is about 0.7 MB, and both App Clip experiences are published. Today I got the same stall without an iPhone. A Mac on an iPhone hotspot on STC mobile (AS39386) ran curl, opening a fresh HTTP/1.1 connection each time: iosapps.itunes.apple.com: IPv6 17 of 231 stalled, IPv4 0 of 89 stalled updates.cdn-apple.com: IPv6 5 of 60 stalled, IPv4 0 of 60 stalled www.apple.com, on a different CDN: IPv6 0 of 115 stalled, IPv4 0 of 85 stalled Each stall looks the same: TCP and TLS finish, the request goes out, and no response byte comes back. The stalls hit many edge addresses. One edge, frmrs1-vip-bx-005, answers on both 2a01:b740:a11:f000::203 and 17.253.122.203, and it stalled on IPv6 only, so this looks like the IPv6 path rather than a bad node. This is one SIM over 17 minutes, and I haven't tested other carriers yet. Repro from a Mac on an STC mobile hotspot: for i in {1..60}; do curl -6 --http1.1 -s -o /dev/null -m 10 -I -w '%{http_code} %{time_starttransfer}\n' https://iosapps.itunes.apple.com/; sleep 4; doneMy questions: Is there anything a developer can do to avoid this or recover from it? Is this a known issue with IPv6 to Apple's edge from Saudi mobile networks? Could someone from the App Clips or edge network team look at FB25380604? It stops real customers at the counter, so it's urgent for us.

We're using AppClips as an important part of our business. Since a few hours scanning the URL assigned to our AppClip shows "AppClip unavailable" instead of the advanced experience! What can we check or do to fix this issue?! We checked Apples AASA CDN and our AASA file and everything is correct. Also, why is this error sheet not showing a link to open the website as it does on older iOSes:

Two advanced App Clip experiences for our app have shown "Received" in App Store Connect since filing, with no action-required flag and no messages: https://go.askdope.com (filed Oct 15) https://go.askdope.com/t (filed Oct 20) What we've verified: The App Clip domain shows as validated in App Store Connect, and Apple's CDN serves our apple-app-site-association file with the appclips entry. The default App Clip experience works, and the app with its App Clip is live on the App Store (version 1.3.3, approved Oct 24). We deactivated three narrower experiences (/app, /events, /positions) to rule out any conflict. Only the two above remain. We submitted 1.3.4 with the App Clip URLs filled in under App Review Information. Result: on an iPhone without the app installed, tapping a go.askdope.com link in Messages opens Safari instead of the App Clip card. Feedback: FB25248311. Developer Support case: 103008003543. Is anything on our side that can hold an experience in "Received"? Has anyone seen this clear, and what moved it? Any pointer from an Apple engineer would be hugely appreciated.

My App Clip shows an image, and I need that image to end up in Apple Notes as a new note with as few taps as possible. The plan is to present UIActivityViewController with the image, then the user taps Notes, then Save. I know clips can’t use PhotoKit, so “Save Image” is likely out. What I can’t find documented is whether Notes, or any other app’s share extension, still shows up in a clip’s share sheet and actually saves. Has anyone tried this? I don’t have a paid account yet to test it myself. If someone could run a one-file test clip, I can send the code.

Good day, I understand a native app is required in order to store hotel keys in Apple Wallet for scenarios where door locks are compatible (https://support.apple.com/en-us/118273). Must this be a traditional, App Store app? Or can this be achieved using an App Clip instead? Thank you very much!

I am experiencing an App Clip domain verification issue in App Store Connect. App: Bini Music Version: 4.1.0 Build: 6 Main App Bundle ID: ninja.wpapp.appbinimusikcom App Clip Bundle ID: ninja.wpapp.appbinimusikcom.Clip Team ID: DY8SYXAUKN Domain: binimusik.com The Associated Domains capability is enabled on both the main app target and the App Clip target with: appclips:binimusik.com The AASA file is publicly accessible at: https://binimusik.com/.well-known/apple-app-site-association The AASA file contains: DY8SYXAUKN.ninja.wpapp.appbinimusikcom.Clip I have also verified the AASA file through Apple's associated-domains CDN, and Apple's CDN returns the correct AASA content and App Clip identifier. Build 6 has been successfully uploaded to App Store Connect and its Binary State is “Validated”. However, in TestFlight → Build 6 → Build Metadata → App Clip → Domain Status, App Store Connect continues to report: Cache Status: Cannot Reach AASA File Debug Status: Invalid Entitlement: Unknown ID The Cache Status has not refreshed and still says: “Cache status updated on Sep 2, 2026 at 3:58 PM.” I checked again on September 7 and the status remains unchanged. Apple Developer Support referred me to the Developer Forums because this appears to require technical assistance. Has anyone encountered “Invalid Entitlement: Unknown ID” with an App Clip even though the AASA file is reachable by Apple's CDN? Is there anything else that needs to be configured, or could this be an App Store Connect domain-validation issue?

Hi All, We build a new feature according to the Apple docs: In iOS 17 and later, App Clips can use the Wallet capability. For more information on functionality that’s available to App Clips, see Choosing the right functionality for your App Clip. and based on that we proceeded with our development, our but in our appclip we are not able to see the wallet capability in the developer portal but for our main application the wallet is there and we enabled it and therefore the com.apple.developer.pass-type-identifiers entitlement has been added to our main app and the appclip, the signing for the main app is working fine, but for the appclip we are getting this issue: Entitlement com.apple.developer.pass-type-identifiers not found and could not be included in profile. This likely is not a valid entitlement and should be removed from your entitlements file.

Uploaded my first App for the app store! Apple said they have a very fast response time but despite their very quick response (only 8hrs after filling out all the paper work), their response felt very generic... basically saying "your a first time app creator we need more information" I responded to all questions and submitted a screen recording of the app and resubmitted for review. It's now been 4 days and no response to my resubmitted review! no email, no notice it was seen... Apple has all these stats about how fast they are to respond but if its just a quick fast initial generic response thats not really a response and its just a way for them to claim a high efficiency. Has anyone else encountered this? How long and how much back and forth should I expect publishing a basic app?

We have a published, approved App Clip that works correctly via QR code and the Safari Smart App Banner, but URL-based invocation does not trigger the App Clip card in any context. Most notably, Apple's own default App Clip URL does not work either: https://appclip.apple.com/id?p=hazel-torus.Clip **Tapping this link in Messages or Notes does nothing. ** Long-pressing it shows a generic website link preview rather than the App Clip card, even though appclip.apple.com is Apple's domain and requires no configuration on our end. Setup details: App Clip bundle ID: hazel-torus.Clip Team ID: 2UNR2APH47 App Clip experience URL: https://passportreader.app/open AASA includes a correctly formatted appclips key with 2UNR2APH47.hazel-torus.Clip (confirmed via https://app-site-association.cdn-apple.com/a/v1/passportreader.app that AASA is correctly cached) Associated Domains entitlements (appclips:passportreader.app) are present on the App Clip target App and App Clip experience are both Approved / Ready for Sale Tested on two physical devices, neither with the full app installed Since QR and Safari banner invocation work, the App Clip itself and its entitlements appear correctly configured. The fact that even Apple's own appclip.apple.com URL fails, and is treated as an arbitrary website link, suggests this may be a backend indexing issue specific to this App Clip rather than a client-side configuration problem. Has anyone else encountered this, or know what could cause appclip.apple.com to not be recognized as an App Clip URL?

I would like to clarify the expected behavior of a default App Clip link regarding tap responsiveness. Issue: When I tap the default App Clip invocation URL in Safari or the Notes app, the first tap does not respond (no App Clip card appears). Only the second tap successfully presents the App Clip card. Steps to Reproduce: Place the default App Clip URL in Safari (or Notes app) Tap the link once → no App Clip card appears Tap the same link again → App Clip card appears as expected Environment: Invocation source: Safari / Notes app App Clip type: Default App Clip experience (appclip.apple.com URL) Observation: This issue reliably occurs when there is no cached App Clip metadata on the device. When the metadata is already cached, the App Clip card appears on the first tap as expected. What I've already checked: Not in Private Browsing mode Question: Is this the expected behavior? Is there a recommended way to make the first tap reliably present the App Clip card even without a pre-existing cache? Thank you for your assistance.

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.

Hi team, We're experiencing two issues with our App Clip invocation via appclip.apple.com links. Setup: App Clip URL: https://appclip.apple.com/id?p=com.x.AppClip The App Clip card and experience work correctly when the full app is NOT installed ✅ Issue 1: App Clip card shown even when the full app is installed When the full app is already installed on the device, tapping the App Clip link shows the App Clip card instead of directly opening the full app. After tapping "Open" on the card, the full app launches — but then the App Clip card appears again on top of the app, requiring the user to dismiss it a second time. Expected behavior: If the full app is installed, tapping the App Clip link should bypass the App Clip card entirely and open the full app directly, routing to the correct screen using the URL parameters. Actual behavior: User taps App Clip link → App Clip card appears (should not appear if app is installed) User taps "Open" on the card → Full app launches App Clip card appears again on top of the full app → User has to dismiss it manually This results in unnecessary friction — two extra taps just to get into the app. Issue 2: Full app does not route to the correct screen When the full app eventually opens (after dismissing the cards), it opens to the default home screen rather than routing to the screen specified by the parameter in the URL. Expected behavior: The full app should handle the URL parameters and navigate to the appropriate screen. Actual behavior: The full app opens to its default/home screen, ignoring the url parameter. Questions: Is this expected behavior that appclip.apple.com links always show the App Clip card even when the full app is installed? If so, is there a recommended approach to bypass the card and open the app directly? What is causing the duplicate App Clip card after tapping "Open"? Is this a known issue, or is there something in our configuration that could be triggering it? For the full-app-installed case, what is the recommended way to handle deep linking from an appclip.apple.com URL into a specific screen in the full app? Should we be handling this via NSUserActivity, UIApplicationDelegate, or a Universal Link handler? Environment: iOS 26.x Xcode 26.x App Clip configured with appclips associated domain Full app and App Clip share the same App ID prefix Any guidance would be greatly appreciated. Thanks!

We ship an App Clip with our iOS app and want the App Clip card to appear when users share our website's links in Messages. Instead, recipients only get a plain link preview. The App Clip was approved and has been live on the App Store for over a week. We've verified every requirement from the docs ("Associating your App Clip with your website" and the Messages invocation requirements): The invocation page's server-rendered HTML (no JS needed) contains the meta tag: apple-itunes-app with app-id and app-clip-bundle-id set correctly. /.well-known/apple-app-site-association has an "appclips" section listing the clip's app ID, and Apple's AASA CDN (app-site-association.cdn-apple.com/a/v1/) serves the same content. The App Clip's entitlements include appclips: and the correct parent application identifier. Via the App Store Connect API, the currently live build contains the APP_CLIP build bundle, and the live version has a default App Clip experience (action OPEN, with localizations). The default experience link https://appclip.apple.com/id?p= returns 200 and shows the clip. Tested in Messages between two devices whose owners are in each other's contacts, in brand-new conversations, on current iOS. However, on-device App Clip diagnostics (Settings > Developer > App Clips Testing > Diagnostics) for the invocation URL show the "App Clip Published on App Store" and "Associated Domains" checks not passing, even though everything above is verified correct. ("No Advanced Experience registered" also appears, but as we understand it advanced experiences are only needed for QR/NFC/App Clip Codes, not Messages.) Has anyone seen device-side association fail like this when the server-side config is demonstrably correct? Is there a known propagation delay after releasing a new app version, or a way to force the device to refresh its App Clip association cache beyond rebooting? Any pointers on what the diagnostics tool checks that isn't covered by the list above would be appreciated.

We have 7 Advanced App Clip Experiences that have been stuck showing "Received" in the App Store Connect UI for 90+ days. However, after inspecting the underlying API response, we can confirm all 7 experiences show "key": "PUBLISHED", "doc_count": 7 on the backend. Despite this, scanning a QR code on a device without the app installed returns "App Clip Unavailable" on every experience. This appears to be a CDN propagation failure — the backend is PUBLISHED but the edge nodes serving iOS devices are returning stale or missing data. Evidence – – App Clip Diagnostics tool shows all green checks for our registered experience URLs (screenshots attached) – App Store Connect UI shows "Received" for all 7 experiences – Backend API response (/appclips/api/v1/experiences) shows: json"statuses": { "buckets": [ { "key": "PUBLISHED", "doc_count": 7 } ] } – iOS devices without the app installed still return "App Clip Unavailable" when scanning QR codes – App version 1.4(6) is live and Ready for Distribution – AASA file is correctly configured and verified – Bundle ID com.goodtrkr.pixlbankar.Clip is correctly associated. Business Impact – This is a production blocker for our AR platform (PixlBank[ar] — Good TRKR LLC). Our entire product delivery depends on App Clip invocation via QR code for enterprise clients. We have been engaged with Apple DTS for 90+ days: TSI Case-ID: 18681098 New Case-ID: 18880040 Feedback Assistant report filed with diagnostic screenshots and sysdiagnose provided no help. REQUEST –  Can an Apple DTS engineer confirm whether there is a known CDN propagation issue affecting App Clip Experiences that are in PUBLISHED state on the backend but not being served correctly to iOS devices? And if so, is there a way to trigger a cache flush or re-propagation for our specific experiences?

I would like to clarify the expected behavior of a default App Clip link. In my testing, the App Clip card was presented even though the full app was installed. Could you please confirm whether this is the intended behavior of a default App Clip link? Environment: Invocation source: Safari / Notes app Thank you for your assistance.

Basic information: The issuer has implemented the feature to active Apple Card via URL Verification. The feature implemented by issuer is supported both in the APP and Clips. When Apple queries the activation method from UnionPay, UnionPay returns the "URL" activation method to Apple. Additionally, the apple-app-site-association file has been correctly deployed, and the configuration for Universal Links has been completed. Both the APP and Clips have undergone testing for Universal Link calls. The desired experiece is that when the APP is installed, Apple Wallet launches the APP, and the user completes the activation within the APP, and if the APP is not installed, Apple Wallet calls Clips, and the user completes the activation in Clips. Problem description: Under iOS 17 and iOS 18, when triggering Apple Pay card activation, the APP or Clips can be called as expected, and the activation can be completed well. However, Under iOS 26, regardless of whether the APP is installed, under the same circumstances, an internal browser within Apple Wallet opens to access the H5 page corresponding to the URL, instead of redirecting to the APP or Clips. Please assist in confirming whether this is a new feature of iOS 26 and how the same user experience can be achieved.

Hey everyone, hoping someone here has run into this before. I have a fully functional App Clip (com.didyoucatchit.app.Clip) linked to my main app (com.didyoucatchit.app). The Clip builds and runs perfectly, but I’m seeing issues trying to enable Apple Pay for it. When I try to link my Merchant ID under the “On Demand Install Capable” capability in the Apple Developer portal, I get this error: A relationship in the provided entity is not allowed for this request. The relationship 'undefined' can not be included in a 'bundleIdCapabilities' request. Here’s what I have already configured and confirmed: App Clip capabilities in Xcode include: Apple Pay Payment Processing Associated Domains (appclips:app.didyoucatchit.com) Provisioning profile includes: Apple Pay Payment Processing Associated Domains In-App Purchase On-Demand Install Capable Entitlements file for the Clip: <key>com.apple.developer.associated-domains</key> <array> <string>appclips:app.didyoucatchit.com</string> </array> <key>com.apple.developer.in-app-payments</key> <array> <string>merchant.com.didyoucatchit.app</string> </array> <key>com.apple.developer.parent-application-identifiers</key> <array> <string>$(AppIdentifierPrefix)com.didyoucatchit.app</string> </array> Merchant ID (merchant.com.didyoucatchit.app) is active and connected to Stripe Stripe Apple Pay configuration matches the same merchant ID and certificate Both provisioning profiles have been refreshed and downloaded However: The portal still throws the “relationship 'undefined'” error anytime I try to modify the Clip’s capabilities In testing, Apple Pay doesn’t show up as a payment option in the Clip (using Stripe’s Payment Element integration) Questions: Is this a known issue with the Developer portal when linking App Clips to merchant IDs? Is there a specific way to re-establish the parent–child relationship between the main app and the App Clip so the bundleIdCapabilities request includes the proper relationship JSON? Are there any additional configuration steps required when using Stripe for Apple Pay inside an App Clip? System Setup: Xcode: 16.2 (build 16C5032a) macOS: Sequoia 15.3.1 iOS: 18.5 (testing on physical device) Merchant ID: merchant.com.didyoucatchit.app Main App ID: com.didyoucatchit.app App Clip ID: com.didyoucatchit.app.Clip Any help or insight would be hugely appreciated Thanks in advance!

We have six Advanced App Clip Experiences configured for our production app, each mapped to a different path under a single domain, each with its own title and image. When a user without the full app installed receives one of these links in Messages, iOS always presents the default App Clip card -- never the matching advanced experience card. The same URLs resolve the correct advanced card in Safari. What we've already verified (so this isn't a basic setup problem): Opening the exact same URL in Safari shows the correct advanced card, including the expected per-path title. A Local Experience (Settings → Developer → App Clips Testing) for the same path + bundle ID validates and launches the correct flow. Associated Domains validation is green in Settings. The AASA at app-site-association.cdn-apple.com contains the appclips component with our App Clip bundle ID, and the applinks components include all six paths. In App Store Connect, all six Advanced App Clip Experiences show "Received" with successful domain validation, and the app + App Clip are live in the App Store. Reproduced on multiple devices on iOS [version], none with the full app installed. Messages does show a card — it's just always the default card. Our questions: Is per-path Advanced App Clip Experience card selection supported in the Messages link bubble at all -- or is Messages documented to always present the default experience metadata regardless of which advanced-experience URL is shared? Apple's App Store Connect help states the default metadata is used "in the app clip link bubble in Messages," which suggests this may be by design -- can someone confirm? If advanced cards in Messages are supported, what conditions cause Messages (but not Safari) to fall back to the default card for the same URL? Does "Received" status indicate an advanced experience is fully live, or is there a later state that confirms Messages rollout? If Messages is expected to always show the default card, we'll plan around that -- we just want a definitive answer rather than continuing to chase a configuration cause. Thanks!

Hello! I am developing an app that includes an app clip. Recently, I launched my app on the App Store, but I discovered that some of the app clip codes are not functioning correctly. My AASA file is configured correctly (general deep links work with it, as well as some app clip URLs) and is also configured for app clips. { "appclips": { "apps": [ "TEAM_ID.maxood.AveBingo.AppClip" ], "details": [ { "appID": "TEAM_ID.maxood.AveBingo.AppClip", "paths": [ "/*", "/bingo/*", ] } ] }, "applinks": { "apps": [ "TEAM_ID.maxood.AveBingo" ], "details": [ { "appID": "TEAM_ID.maxood.AveBingo", "paths": [ "/", "/bingo/*" ] } ] } } I've also created the advanced app clip experience in App Store Connect and configured it to open links with my domain as the prefix: So if I create an app clip code with my root URL 'https://avebingo.com', my app clip is immediately launched. However, if I create an app clip code and want to launch my app clip for a particular bingo using the URL 'https://avebingo.com/bingo/<some_id>', it is not launched, and a popup says, 'This app clip is not currently available in your country or region.' Interestingly, app clip diagnostics in my iPhone settings indicate that everything is okay for my root URL. But for URLs like 'https://avebingo.com/bingo/some_id', it says the following, which indicates that my app is not launched in the App Store (but it is). Can you please share what do i do wrong and how to fix it? Thanks in advance.

Every time I create an update for my application, the "App Clip" section on the "App Information" page on App Store Connect "forgets" the app clip information entered for the previous version. There used to be an "Apply previous" button in this section but it appears to have disappeared? Is there a way I can determine if this is a bug or if something in my configuration changed? I'm not even sure what I would provide if I filed this as a bug report.