I created an application with the com.apple.developer.web-browser (set default browser) function, but when I want to add the Universal link function to this application, I found that the Universal link function is invalid. I searched for this problem for a long time, until finally I found that it has something to do with com.apple.developer.web-browser settings, when I turn off com.apple.developer.web-browser, Universal link works again. But my app needs to have both, has anyone encountered such a problem? Can you provide some solutions?Thanks anyway.

Hello everyone. My team and I are having trouble getting our app approved by the review team. They keep rejecting our app because they are unable to open a Deep link (magic link) sent via email and used to trigger the user authentication. The problem seems to be only on iPad since they confirmed a successful login through iPhone. We tested the app via TestFlight on 2 physical iPads (same iOS version the review team Is using and said we should test against) and 2 simulated iPads and the Deep link always work for us consistently, we even sent them a screen recording of the working process. We are really struggling to understand what can be the source of their ina inability to open Deep links. Has anyone encountered such problem before or has any idea what may be causing It? Thanks

Hi, does anyone know of a service that will generate QR codes that contain Universal Links so that we can deep link into specific areas of our iOS app? I have my app code set up to deep link and the requisite apple-app-site-association file ready to go, but I cannot find a QR code generator that will allow us to enter an Apple Universal Link. One service, Scanova, has relayed to us that we have to create a URI that will tell their system to redirect to a web page containing the Universal LInk, which seems to defeat the purpose as Universal Links are supposed to be direct. So is this possible to do at all or we have to go the route Scanova indicates? thanks for your help in advance & cheers, Gordon

Hi, I am running into a strange issue where my universal links work fine on devices when using USB, simulators and TestFlight, it works with no problem on all test environments But once I submit it for App Review, they don't work. And I have no way to replicate it. At some point they get it working somehow but every resubmission the process repeats where I go back and forth for days until they finally get it working. Anyone run into this strange issue or has a clue what might be going on?

Hi everyone, I am trying to find documentation to understand how many users visited your app after clicking universal links on mobile web. Can you please point me to the right resources? Is this data readily available in our app store account?

We have been testing universal links and detected the following: Assuming there is an HTML with embedded JS that redirects to the universal link. **Direct redirection --> WORKS OK ** window.location.href = "https://my-universal-link?data=abc"; Redirection with timeOut or Interval --> NOT WORKING (go to default WEB) setTimeout(function () { window.location.href = "https://my-universal-link?data=abc"; }, 2000); setInterval(function () { window.location.href = "https://my-universal-link?data=abc"; }, 2000);

i implemented universal url support in iOS app where when we click on universal url, app was getting open in iOS 16.1 and below this OS version Problem is: when same link we open from iOS 16.5 and iOS17 beta version, it is not opening app. it is opening browser instead. my question is what happened with iOS 16.5 and above are they not supporting universal url?

Hi We locate the file apple-app-site-association on both https://ourdomain.com/apple-app-site-association and https://ourdomain.com/.well-known/apple-app-site-association By visit this two urls, we are able to get file content through browser. We are able to get the file content through https://app-site-association.cdn-apple.com/a/v1/ourdomain.com with US based IPs, Europe based IPs. However, if we visit this url with Asia based IPs, we always got 404 with content Not Found. Some work CDN nodes: < Via: http/1.1 ussjc2-vp-vst-009.ts.apple.com (acdn/14319.5), http/1.1 ussjc2-vp-vfe-002.ts.apple.com (acdn/14319.5), https/1.1 usscz2-edge-lx-004.ts.apple.com (acdn/14319.5), https/1.1 usscz2-edge-bx-033.ts.apple.com (acdn/14319.5) Via: http/1.1 ussjc2-vp-vst-009.ts.apple.com (acdn/14319.5), http/1.1 ussjc2-vp-vfe-002.ts.apple.com (acdn/14319.5), https/1.1 usscz2-edge-lx-004.ts.apple.com (acdn/14319.5), https/1.1 usscz2-edge-bx-033.ts.apple.com (acdn/14319.5) which return file content in apple-app-site-association with response code 200. Some not work CDN nodes: < Via: http/1.1 jptyo5-vp-vst-014.ts.apple.com (acdn/84.14362), https/1.1 jptyo5-vp-vfe-006.ts.apple.com (acdn/84.14362) which return Not Found with response code 404. When use Asia based IPs, we also got some error response header: < Apple-Failure-Details: {"cause":"context deadline exceeded (Client.Timeout exceeded while awaiting headers)"} < Apple-Failure-Reason: SWCERR00301 Timeout Example request with IP in Japan: > GET /a/v1/ourdomain.com HTTP/1.1 > Host: app-site-association.cdn-apple.com > User-Agent: curl/7.86.0 > Accept: */* > * Mark bundle as not supporting multiuse < HTTP/1.1 404 Not Found < Content-Type: text/plain; charset=utf-8 < Content-Length: 10 < Connection: keep-alive < Server: nginx < Date: Mon, 21 Aug 2023 12:45:02 GMT < Expires: Mon, 21 Aug 2023 12:45:12 GMT < Age: 608 < Apple-Failure-Details: {"cause":"context deadline exceeded (Client.Timeout exceeded while awaiting headers)"} < Apple-Failure-Reason: SWCERR00301 Timeout < Apple-From: https://ourdomain.com/.well-known/apple-app-site-association < Apple-Try-Direct: true < Via: http/1.1 jptyo5-vp-vst-014.ts.apple.com (acdn/84.14362), https/1.1 jptyo5-vp-vfe-006.ts.apple.com (acdn/84.14362) < X-Cache: MISS KS-CLOUD < CDNUUID: 03f2e102-fa68-4a5f-bc93-0e151a3dfc64-773587498 < x-link-via: ziyct01:443;xymp07:443;gzun11:443;xg02:443; < x-b2f-cs-cache: no-cache < X-Cache-Status: MISS from KS-CLOUD-XG-02-03 < X-Cache-Status: MISS from KS-CLOUD-GZ-UN-11-06 < X-Cache-Status: MISS from KS-CLOUD-XY-MP-07-15 < X-Cache-Status: MISS from KS-CLOUD-ZIY-CT-01-09 < CDN-Server: KSFTF < X-KSC-Request-ID: 0afe4d526afd86918a55a0640d2b75f3 < X-Cdn-Request-ID: 0afe4d526afd86918a55a0640d2b75f3 < Not Found

I have a question regarding the "webcredentials" field in the "apple-app-site-association" file. If there are multiple apps listed in webcredentials, do the credentials for one app need to work for the other apps? I created an app without a web version and I am using the associated domain "webcredentials:website.com" to enable password autofill. I am wondering if I will be able to use the same associated domain for other apps in the future even if the credentials aren't shared between apps. (I tried using a subpath "webcredentials:website.com/app1", but the subpath isn't used when looking at Settings -&gt; Passwords) Thank you,

Hello, I'm currently configuring Universial Link to my services. But I've got error(SWCERR00201) from apple CDN. $ curl -I -v https://app-site-association.cdn-apple.com/a/v1/m.qa.music-flo.com ... < Apple-Failure-Details: {"location":"http://m.qa.music-flo.com/.well-known/apple-app-site-association/"} Apple-Failure-Details: {"location":"http://m.qa.music-flo.com/.well-known/apple-app-site-association/"} < Apple-Failure-Reason: SWCERR00201 Insecure (non-https) redirects forbidden Apple-Failure-Reason: SWCERR00201 Insecure (non-https) redirects forbidden < Apple-From: https://m.qa.music-flo.com/.well-known/apple-app-site-association Apple-From: https://m.qa.music-flo.com/.well-known/apple-app-site-association ... However, I can get apple-app-site-association json file via accessing http/https URL(http:/m.qa.music-flo.com/.well-known/apple-app-site-association). I would greatly appreciate any help on this. Thank you !

My iOS app has to support a universal links to a specific page in the app when it clicked outside the app. The app we have built is not a native iOS app but it get loaded in iOS shell or frame. Below is the scenario which i am facing the issue. Landing page URL https://example.domain.com/#/ Specific links https://example.domain.com/#/ncx/view-post/:1234 The above link if I clicked outside the app it should go to the specific post but it currently open the app but not going to specific page. I have tried below formats in AASA file but it did n't work out And I am having difficulties in getting this to work. I have created an AASA file like { "applinks": { "apps": [], "details": [{ "appID": "ASDF35SDF.ios.mybundle.com", "components": [{ "/": "/#/ncx/*" }] }] } } I also tried with wildcards instead of directly adding "#" in the AASA file. { "applinks": { "apps": [], "details": [{ "appID": "ASDF35SDF.ios.mybundle.com", "components": [{ "/": "//ncx/" }] }] } } Both didn't work. Any help is appreciated. Update 1 Tried with new fragment components, but no luck there either { "applinks": { "apps": [], "details": [{ "appID": "ASDF35SDF.ios.mybundle.com", "components": [{ "#": "/ncx/*" }] }] } }

CDN Cache URL: https://app-site-association.cdn-apple.com/a/v1/dev.alignwell.com Apple CDN Cache Checks: Fail CDN Cache Query Success: Fail Status Code not 200-299: 404 No Apple Failure Message: Fail Apple has provided a failure reason: SWCERR00201 Insecure (non-https) redirects forbidden Apple CDN Cache Up to Date: Fail File cached by Apple CDN does not match direct file CDN Cached Contents: Not Found Apple CDN Debug Headers: Apple-Failure-Details: {"location":"http://dev.alignwell.com/.well-known/apple-app-site-association/"} Apple-Failure-Reason: SWCERR00201 Insecure (non-https) redirects forbidden Apple-From: https://dev.alignwell.com/.well-known/apple-app-site-association Apple-Try-Direct: false Cache-Control: max-age=3600,public Age: 3561 Content-Length: 10

Universal linking feature stooped working after adding smart app banner. Also, universal linking started working after removing Smart app banner meta tag from the website. To test smart app banner on staging env, we used appStoreId of our prod app that is on appstore because we don't have a stage app on app store. Both universal links and Smart app banner are working fine on staging env but the same flow is not working on prod env. Any help would be appreciated

Hi, I have a problem with associated domains developing Passkeys app. Adding alternate mode(developer mode) to Associated Domains Entitlement, it works fine. But in non developer mode, CDN doesn't seem to read the AASA file. AASA file's path is: https://(host).(rootdomain)/.well-known/apple-app-site-associtation I checked the TLS certificate conditions and all conditions are met. https://support.apple.com/en-us/HT213464 https://support.apple.com/en-us/HT210176 https://support.apple.com/en-us/102028 Is there another reason why it only works in developer mode? Thanks for your reply.

I uploaded the AASA configuration file to two domains - one domain consists of Cyrillic, the other domain consists of Latin letters. The problem is that a domain that supports Cyrillic is not handled when opening a link in iOS app. The AASA configuration is the same. Does apple support universal links for punycode domains ?

Investigate why your universal links are opening in Safari instead of your app. View Technote TN3155 >

Recently, it has been discovered many times that after newly installing the mobile cloud disk APP on the IOS system, the universal link c.139.com (for example: https://c.139.com/m/a/s/?p=L1t4) cannot be used. Pull up directly. After our internal monitoring and analysis, the situation is as follows: Monitoring data shows that recent visits to Apple’s CDN configuration files (https://app-site-association.cdn-apple.com/a/v1/c.139.com, https://app-site-association.cdn -apple.com/a/v1/yun.139.com), a 404 error is often reported, that is, obtaining the configuration file from Apple CDN back to the source c.139.com and yun.139.com fails. The number of alarms is 2-3 times a day, and each time lasts for 1-2 hours. As a result, newly installed or upgraded IOS mobile cloud disk clients during the corresponding period cannot pass c.139.com and yun.139.com. The domain name directly launches the APP. After our operation and maintenance inspection, there are no abnormalities in the c.139.com server file configuration and network, and the universal link of the client's project configuration is also correct. We need Apple's help to check whether there are any abnormalities in the routing of Apple's CDN nodes to 117.161.4.213, and to check whether there is instability in the CDN nodes. Thank you so much.