Hi Apple, We have been using Associated Domains and Universal Linking for years now, without any problem. Recently, users began having problems accessing the app through Universal Links. A quick look in the swcutil_show.txt file (through Analytics gathering in the sysdiagnose) at what the system tried to download revealed that the Apple Server had issues downloading our AASA file: Error Domain=SWCErrorDomain Code=7 "SWCERR00101 Bad HTTP Response: 502 Bad Gateway -- {"status":"502 Bad Gateway"}" UserInfo={Line=275, Function=-[SWCDownloader URLSession:dataTask:didReceiveResponse:completionHandler:], NSDebugDescription=SWCERR00101 Bad HTTP Response: 502 Bad Gateway -- {"status":"502 Bad Gateway"}, UnderlyingError=Error Domain=HTTP Code=404 "(null)" UserInfo={Line=275, Function=-[SWCDownloader URLSession:dataTask:didReceiveResponse:completionHandler:]}} I was wondering if there was ANY way of knowing what cause the 404? Thanks!

Hi guys! I'm using a universal link to match with iOS and Android. I'm trying to open my app when user clicks in a link like this: https://mywebsite.com/?invite=TI878IU I've tried many different ways to create the file apple-app-site-association. But any of them I could use this parameter directly. Do you have any guidance in how I could do that? This is my file: { "applinks": { "apps": [], "details": [ { "appIDs": [ "ABC12345AB.com.example.app" ], "paths": [ "*" ], "components": [ { "/": "/*", "comment": "Matches any URL with a fragment parameters to open it as universal link" }, { "/": "/privacy.html", "exclude": true, "comment": "Matches any URL with a path that starts with /help/website/ and instructs the system not to open it as a universal link." } ] } ] } }

I have a punycode link of the following type: https://xn--d1aqf.xn--p1ai/.However, clicking on this link, or opening it through the simulator, opens the page in the browser, not in the application. The system does not see that this domain is present in one of the applications, however, any other domain (example.com , for example), is validated by the system. What could this be related to?

Hello, I work for an email marketing company where we send emails through SendGrid. The links go to ebay.com. SendGrid will wrap the links for click tracking purposes, so instead of the link appearing as https://www.ebay.com, it will be something like https://u99798501.ctc.sendgrid.net/... which will then redirect to eBay. We've noticed that when clicking on these SendGrid-tracked links that redirect to eBay, the links do not open in the eBay app, even though we have the eBay app installed. They will instead open up in Safari. Clicking on the https://www.ebay.com links without the wrapping will open in the links in the eBay app. This makes me think that the URL being wrapped by another URL is preventing Universal Links (links opening in the app) from working. However, we're pretty sure this did work at one point. Does anyone know the status of Universal Links with wrapped URLs? Did it change recently? The iOS version that we tested with is 17.5.1. We are opening links from the iOS Gmail app. Thank you!

My SampleApp, named "myApp," already supports deep links such as "https://myApp.com/tab/record/10020." When this link is clicked, it navigates to myApp, and AppDelegate handles the further process. Now, I need to support another link (domain), "https://appcloud.com/tab/record/10020," so that clicking this link also navigates to myApp. Is there any way to solve this kind of problem without adding "apple-app-site-association"?

Hello, My App use OIDC for user authentication and universal linking for redirection from browser to App. When user use autofill to enter credentials, sometime autosubmits happens automatically and after successfully login user sticks in the web. No redirection in the App happens in this situation. Could you please look into it? In my view universal linking/redirection should work even on autosubmit.

Universal links stopped working lately. Nothing has changed in our code nor in the "apple-app-site-association" file. We use it for years and it suddenly stopped working. Any ideas?

Hi, Can a single domain serve a /.well-known/apple-app-site-association file for multiple apps from different developers? We currently have our own domain, let's say example.com, which serves https://example.com/.well-known/apple-app-site-association which lists our app, let's say "ABCDEFG.com.example.AppA" for path "/app/a". We're talking with another developer who has another app on the store. Can we add their app, "MNOPQR.com.different.AppB" on our site, https://example.com/.well-known/apple-app-site-association, add their app ID for path "/app/b", ask them to add our example.com domain in their associated-domains entitlement, and would it work? I mean would https://example.com/app/a open our app "ABCDEFG.com.example.AppA" and https://example.com/app/b open their app "MNOPQR.com.different.AppB" ? We want to open https://example.com/redirect/app redirect to either /app/a or /app/b depending on the query parameters and launch our or their app. Thanks in advance!

I've setup applinks for Universal Links purposes on my app. But I noticed that setting up applinks also sets up Password AutoFill. Upon logging in I don't want my users to be prompted to Save Password because of the way we use our subdomains. How can I disable Password AutoFill while retaining Universal Links capability, and without disabling secureTextEntry on my UITextField?

I have configured AASA file to support path such as https://domain/forgot-password?token=asadsad3ddsd. It is not opening in browser nor app. I have tried different iterations to support the above url. iteration 1 : components : [ { "/" : "/forgot-password" , "?" : { "token" : "?*} ] iteration 2 : components : [ { "/" : "*" } ] iteration 3 : components : [ { "/" : "/forgot-password" , "?" : { "token" : "?????..." } ] my token is of length 36. so I have kept 36 question marks. do we need to configure something in flutter app delegate to support query parameters.

An archived documentation article about Universal Links, https://developer.apple.com/library/archive/documentation/General/Conceptual/AppSearch/UniversalLinks.html states: "In your com.apple.developer.associated-domains entitlement, include a list [...], prefixed with applinks:, such as applinks:sub.mywebsite.com. Limit this list to no more than about 20 to 30 domains." This document was updated last in 2016 and it appears to be archived since 2018. Newer documentation, like https://developer.apple.com/documentation/xcode/supporting-associated-domains or https://developer.apple.com/documentation/xcode/configuring-an-associated-domain do not mention any limitations and since iOS 14 there is also an Apple provided CDN that apps use to fetch domain association data, which lets one think that the limit may have been lifted. However, I'm in the process of implementing universal links and shared web credentials for a portal app with many customers, a few hundreds of them have their own domain, and would like to be sure this is supported before putting all the work into it. So if anyone with a similar setup or someone from Apple could share/verify that there is no such limit anymore (or if any, what number) I would highly appreciate it. Bests bbjay

THE ISSUE - Hi there guys we have been through documentation and gone back and forth on forums and we can not get universal links / Deep link to work for us. OUR SETUP - We are running Flutter and are looking to post images from the Gallery into the app only issue is it does not pick up the page its meant to open once the share button is clicked. We have tired all the steps meticulously and still can not get it to work. Are they any known issues with this ?

Hello, my app was rejected because deep linking doesn't work as expected according to the reviewer. I have reinstalled the app and tested it on the same device and iOS version as the reviewer, but everything still works fine for me. I also asked a few friends (three people) to test it, and they all confirmed that the deep linking works as intended. Have you ever experienced a similar issue before, or do you have any insight into why this might be happening? Thank you in advance.

I have managed enterprise app. universal link is working as expected from the safari but when I tried the same functionality from the managed edge browser, edge does not detect the universal link. Unable to open our managed app from the edge browser, although from the safari it's working as expected. Unable to open our managed app from the outlook/Team. although from a non-manged app, we can open our managed app. Does edge browser support universal link? iOS version : 17.4.1

Hi, I have added associated domains support for our desktop app and it works fine on my machine. But when I deploy it on other machines, it is not launching. It throws ‘The application ““ can’t be opened” message. It works fine when I install provisioning profile on those machines. Xcode is not allowing me to code sign the app manually as part of build process. Till now we were dong the same for other apps. Associated domain need a provisioning profile and I have created one distribution profile and code signed it. Now it works fine only on my machine and not working on other machines. It works only on other machines if I install provisioning profile. What should be the issue? How do I work this macOS app on other machines without installing provisioning profile?

We've got a AASA file on our site that has a list of URLs that our App can handle. These URLs follow a REST standard, but also have resource identifiers in them, for example /site/:siteId /site/:siteId/service/:serviceId Our service IDs are limited to specific numbers, which we've hardcoded in our AASA file so that only specific service URLs will open. Our AASA file looks like the below { "applinks":{ "apps":[], "details":[ { "appID":"${appIdPrefix}.${bundleIdentifier}", "paths":[ { "/":"site/*/service/1/" }, { "/":"site/*/" } ] } ] }, "webcredentials":{ "apps":[ "${appIdPrefix}.${bundleIdentifier}" ] }, "appclips":{ "apps":[ "${appIdPrefix}.${bundleIdentifier}.clip" ] } In this example, hitting a URL like /site/1/service/1 works correctly - however, hitting a URL like /site/1/service/999 will also open the app, despite it not being a valid URL. I'm assuming that the wildcard on site/*/ is causing the invalid URL to match. How can I set my AASA up so that the site ID can still be any value, but the URL is matched strictly?

This page describes the procedure to create deep links in iOS. I was able to launch an IOS Companion app (name of the app in my case) using its deep link. But the same is not working in AppleWatch. This is my plist to register a custom scheme - Companion: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>CFBundleURLTypes</key> <array> <dict> <!-- <key>CFBundleTypeRole</key> <string>Viewer</string> --> <key>CFBundleURLName</key> <string><some unique ID></string> <key>CFBundleURLSchemes</key> <array> <string>Companion</string> </array> </dict> </array> </dict> </plist> I have implemented onOpenURL(perform:) to handle app launches using a deep link (url). var body: some Scene { WindowGroup { ContentView() .onOpenURL(perform: { (link: URL) in Log(String(format: "Link = %@", link.absoluteString)) // Use then deep link }) } } In iOS, I tested deep links in two ways: Wrote the full deep link in Notes app and tapped it. Created another app called AppLauncher with a Button saying 'Launch using Deep link'.... which when clicked opens the deep link using open(_:options:completionHandler:). Both the approaches work in iOS, but in watchOS, I can only try 2 because Notes app is not available for AppleWatch. So, I created another watchOS app called AppLauncher, which displays a SwiftUI Button saying 'Launch using Deep link', which when tapped, tries to open the link using openSystemURL(_:). But as mentioned in the documentation (linked earlier), Opens the specified system URL. this API only works for links associated with System apps i.e., Apple's call and message apps. So, how else can I use deep link to launch another app? I believe it's possible to launch an app using its deep link because the info.plist keys required to define a deep link scheme association (CFBundleURLTypes, CFBundleURLSchemes etc) is valid for watchOS too.

I have an application which supports universal links. Say it supports the domain www.example.com and thus universal links can be easily opened via this. We will have applinks:www.example.com in associated domains. Now say if I want to release another app and it also supports the same domain. Now how will iOS distinguish which app to open via universal links..?

Subject: Inquiry Regarding Placement of .well-known Folder for Hosting apple-app-site-association File I am writing to inquire about the placement of the .well-known folder for hosting the apple-app-site-association file. Currently, we are working on configuring deep linking for our iOS app, and we have encountered a question regarding the appropriate location for hosting the apple-app-site-association file. Our domain, service2-uat.mom.gov.sg, hosts various web assets, and we are considering placing the ".well-known" folder in a non-root directory, specifically at "https://service2-uat.mom.gov.sg/fwmc/api/stg/permanent/.well-known/apple-app-site-association", instead of the root directory. Before proceeding with this configuration, we wanted to confirm whether it is permissible and supported by Apple's specifications and requirements. Our objective is to ensure compliance with Apple's guidelines while optimizing our server structure. Could you please provide guidance or clarification on whether hosting the .well-known folder in a non-root directory is acceptable for serving the apple-app-site-association file? Additionally, if there are any specific considerations or best practices related to this configuration, we would greatly appreciate your insights. Thank you very much for your assistance in this matter. We look forward to hearing back from you soon. Best Regards, Senthil S

The universal link for my app was working perfectly fine 2 days before but suddenly it stopped working. We have not changed applinks, or AASA file for long time.