Hi everyone, I’m trying to launch an App Clip for my app, and I’ve been stuck trying to debug why the App Clip won’t launch in production, despite everything seemingly being set up correctly. My setup: Main app bundle ID: com.release.cosa App Clip bundle ID in Xcode: com.release.cosa.appclip In App Store Connect, the App Clip is listed as: com.release.cosa.appclip My AASA file (served with correct headers from my domain): { "appclips": { "apps": ["com.release.cosa.appclip"] } } App Clip target and entitlements are properly set in Xcode What works: App Clip launches via local testing in Xcode (Simulator and physical device) App Clip works when triggered manually from Safari (while debugging) What doesn’t work: NFC tag or Universal Link from the real world does not trigger the App Clip On device, nothing happens – not even a fallback to Safari No errors shown to user

Question: I'm aware of the AASA file hosting procedure to make app clips work and link them to your website, but IIRC you can trigger app clips via the simple appclip.apple.com URL too, right? As a result no need to host the AASA file. Like my app store connect gave me the URL https://appclip.apple.com/id?p=myname.myappsname.Clip but when I click it it says "This app clip is not currently available in your country or region". However I'm also getting Bad JSON content on the View Status under the domain. I'm so confused.

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?

Hello, I am new to App Clip development. I have uploaded a build with app clip to App Store Connect and the build is visible on the TestFlight. I am able to open the App Clip via TestFlight and I do see everything working, but the app clip is not getting added in Recent Apps folder and is no where found on the device. If I want to launch the app clip again, I have to scan the QR code again. When I use other app clips, like Panera Bread, the app clip stays in my Recent App/Recently Added folder. My app clip size is close to 75MB. Is the app clip not in Recently Added folder because the app clip is installed from TestFlight or is it happening because of the app clip size? Thanks!

为什么App 上传testFlight之后。无法通过NFC的方式唤醒 APP Clips。是必须要上架商店之后才能支持么？

My App Clip is associated with three domains: • nfc.ttwifi.net • qr.ttwifi.net Currently, I’m experiencing an issue where scanning a QR code from qr.ttwifi.net correctly launches my App Clip. However, when I scan a QR code from nfc.ttwifi.net, it successfully displays the App Clip card but then shows the message “App Clip unavailable.” I checked the Website Status in App Store Connect, and both domains have their Debugging Status and Cache Status marked as Verified. One important detail to note: Yesterday, while submitting a new version for review, I noticed that nfc.ttwifi.net showed “Unable to connect to AASA file” in the Cache Status in App Store Connect. The cache status update time was March 27, 2025, at 6:52 PM. However, when I checked today, both domains appeared to be fine, and the cache status update time was March 27, 2025, at 7:07 PM. How can I restore the App Clip functionality for my nfc.ttwifi.net domain?

I just started with App Clips so quite new to it. One of our dependencies is very big in size (85+ MB) which is making the app size almost 87MB's uncompressed and 40MB's compressed with just this dependency and no other app clip related code in it. I created a App Thinning size report for the app clip and even with bigger app clip size, I decided to upload the beta build to App Store Connect for testing purposes. On App Store Connect, app clip size is 70+ MB and to my surprise it passed the App Store Connect review and I was able to install this app clip on my device from Test Flight. If I add functionality to the app clip with this bigger dependency SDK, then the app clip size is going to increase further and am worried that it could get rejected when I push it to app store. Minimum iOS version of the app is 16.4, so my understanding is that the maximum app clip size allowed is 15MB. Am trying to figure out, how the app clip build was approved on app store connect and if dependency sizes in app clips are ignored? Attaching screenshot of App Thinning report and screenshot of App Store Connect build with this App Clip.

I created an App Clip for my app and added the necessary meta tag to my website. When I initially opened the URL in Safari, the App Clip card appeared and worked as expected. However, after tapping "Show in Safari" on the App Clip card once, it never appeared again. Now, I only see the App Clip banner at the top of the page, but the full card does not show up anymore. Is this expected behavior and is there a time limit before it can be shown again?

My main app does have entitlement to access Coretelphony, i would like to use the same with Appclips, though i was able to add the entitlement to appclip profile, i am unable to create archive for Testflight, i am seeing missing esim profile capabilities, is this not supported in appclips at the moment?

I have an app binary (com.BinaryJigsaw.PlanHub) that includes an app clip that has been reviewed and approved. I have three domains in the associated domains, set in xcode. I have my AASA file up and running on my planhub.app domain (not the others yet - just trying to get this one working first!), but I am not able to set up an app clip experience. When I enter the URL (https://planhub.app) in App Store Connect I get: "This URL is not contained in your app’s associated domains. Update associated domains or use a different URL." If I look at the domain URL status for the build it says: "Cannot Reach AASA File". That seems to be incorrect as I run this test from terminal and get a 200 response and the json file is returned. curl -v https://app-site-association.cdn-apple.com/a/v1/planhub.app The bundle IDs in the AASA file match my app and app clip. Any help appreciated!

I integrated an Advanced App Clip Experience to my app. In trying to test the App Clip Card, the card does not appear when I tap the link on my device that is associated to the Advanced App Clip Experience. Listed are some contextual information: Testing on device running on iOS 18.3.1 Associated Domains: Main target app: applinks: App clips target app: applinks: and appclips: Archived and uploaded build to App Store Connect. Green "Testing" status via Testflight. On Distribution tab, green "Valid" status for build domain. Advanced App Clip Experience green "Received" status. Developer App Clip Testing Diagnostics: Green "Register Advanced Experience" status Green "App Clip Code" status Warning "App Clip Published on App Store" Orange Circle "Associated Domains" After looking at countless threads, I still cannot for the life of me find a solution to test the App Clip. Any guidance would be extremely appreciated. I had also submitted a support ticket with case ID #102552504973.

Hello! We are writing as we recently have started receiving complaints that the app clips QR codes aren't working well. Users scanning QR codes will be taken to the website, where they don't even get the app clip banner. It seems to be a recent change, as we started getting complaints about it. I have also noticed this on IOS 17 and IOS 18 devices. Our application with this app clip has been live for over a year and we haven't had issues before. Example 1: The user scans an app clip QR code, but sees url and opening just loads the website. It doesn't show even the app clip banner. After moving back to the camera app and rescanning the QR code it shows the app clip correctly. Also now going back to the website shows the banner popup. Example 2: I scan app clip QR code. It shows just the website url. I scan another app clip QR code it loads that correctly. Now when I scan the first app clip QR code again it shows it also correctly now. Example 3: I scan app clip QR code. It shows website url instead of app clip. When I open IOS control center and close it then the camera app refreshes and it shows the app clip button instead the web link. I have videos of all of these cases that I could upload somewhere if needed. As it seems some links are not allowed here. Let me know if you need any more input.

Over the past two weeks, we have noticed widespread degraded performance in iOS devices not recognizing when links are App Clips. When scanning the QR code, it identifies it as a link, not an App Clip link and tries to open the link via Safari. Once in Safari, it still prompts the user to download the full app and not open the App Clip. Scanning with the Control Center "Scan Code" button gives an indication that it understands it's an App Clip link, but still does not open it correctly. In some cases, it will say "App Clip Unavailable" which is simply not true. After a few scans of the same QR code, the iOS device will correct itself and open the correct App Clip. There is no consistency and/or reason why it would do this. We have had a massive influx of users complaining that it's not opening the App Clip correctly. We have not changed anything on our website or app that would alter the efficacy of this issue. Have tested on a variety of different iOS devices on a variety of different operating systems (iPads, iPhones, iOS 16, iOS 18, etc) and they all have started behaving this same way. In addition, we've tested on other apps with App Clips and they are experiencing the same issue. My guess is that there is something happening on Apple's side with apple-app-site-association issues. We reported via Feedback Assistant but have yet to hear from anyone from Apple to acknowledge this is a widespread issue.

I have an App Clip that uses SKOverlay.AppClipConfiguration to install the full app. Before I added a Live Activity call (Activity.request), the user could see “Install,” then “Open.” Now, once “Get” is tapped, the Clip immediately closes—no “Open” button appears. If I remove the Live Activity code, it works again. I’ve confirmed that parent/child entitlements match, and tested via TestFlight. Is there a known issue or recommended workaround for combining SKOverlay + Live Activities in an App Clip so it doesn’t dismiss prematurely? Any insights are appreciated! Note live activity is for App Clip only.

I found that when the development tool above Xcode16 ran my app, I opened the suspended inscription function, and then opened the system camera, the content in the suspended window would not be displayed, and the suspended window would have a black screen. However, this phenomenon does not appear on Xcode15.4 development tools, it is the same code, I do not know why

A few days ago scanning NFC tags or QR codes for AppClips with advanced experiences started showing the error "The operation couldn't be completed. (CPSErrorDomain error 2.)" in the AppClip sheet as seen here: We are providing AppClips to our customers and they trust AppClips to always work, since it is a big part of their business. Since this is happening at our customers phones and on the phones of their customers, I don't have a sysdiagnose. I already created a feedback entry about this FB16601674. We checked everything, our AASA file, the Appstore Experiences.

I have a SwiftuI App which includes an App Clip. There is one target for the iOS app and one for the App Clip. All good. But I want to create a new target for the test flight app so that test users can distinguish it from the App Store app. E.g. Test Flight app has a different icon asset file in the target but is identical in all other aspects. However, when I try to build the test flight target I see the message: The com.apple.developer.parent-application-identifiers entitlement (...]') of an App Clip must match the application-identifier entitlement ('...') of its containing parent app. This implies that I’d have to change the entitlement of the app clip, which would mess up the production version so I clearly don’t want to go that route. Any ideas how to overcome this conflict?

I have a SwiftuI App which includes an App Clip. There is one target for the iOS app and one for the App Clip. All good. But I want to create a new target for the test flight app so that test users can distinguish it from the App Store app. E.g. Test Flight app has a different icon Asset file in the target but includes all the other source code files. However, when I try to build the test flight target I see the message: The com.apple.developer.parent-application-identifiers entitlement (...]') of an App Clip must match the application-identifier entitlement ('...') of its containing parent app. I can't figure how to do this without messing up the original production App. Any ideas?

My app helps users connect to Wi-Fi networks, and I have requested the Access Wi-Fi information entitlement. This allows the app to retrieve the current Wi-Fi information to ensure the user’s connection is successful. Now, we are trying to implement an App Clip that enables users to connect to a specific Wi-Fi network through a QR code scan or NFC in certain scenarios. In the App Clip, I’ve requested the Hotspot entitlement, which allows the app to use the hotspot manager to configure Wi-Fi networks. However, since I cannot access the current Wi-Fi information in the App Clip, I’m unable to confirm whether the connection was successful.

In our app clip, we open/show the full app download banner. We used to have the expected behavior, but with seemingly no changes to the app download banner code we have the following issue. Expected behavior: App download banner shows in app clip, user presses "Get" button, app is downloaded and installs, "Get" button changes to "Open" button (note: button is blue), user presses "Open" button and the full app is opened. Current behavior: App download banner shows in app clip, user presses "Get" button, app is downloaded and installs, "Get" button changes to "Open" button (note: button is now grey), user presses "Open" button but nothing happens. With the current behavior, the full app is correctly downloaded and the appclip removes itself from the phone, but the open button does nothing.