iOS Apple App Site Association(AASA) file debugging/troubleshooting for universal links
ฝัง
- เผยแพร่เมื่อ 10 ก.ค. 2021
- In this video, we will learn to debug and troubleshoot the apple-app-site-association file to find out whether the device has initiated the request or not and downloaded the AASA successfully.
We will learn to find the exact error which might lead to issues in universal linking.
Also, we will learn to use console and system diagnose files for out further debugging purposes
Awesome video! Thank you very much for the walkthrough. It really helped me find out what was going on.
very helpful, thank you Rajan!
Excelent video!! Thanks you very much!!!
Really a big help, thanks you
Awesome video! Thanks.
thanks Rajan, really helpfull
This helped a lot!! Thanks
Glad to hear it!
good
Hi, swcutil is showing site/fmwk approval as denied for my app. Could you please help what is wrong with my AASA?
Hi, This has to do something with your site where you have hosted AASA. Possibilities can be anything. May be your site or the address you are accessing is private.
Check your appID format. It should be object first and not array. Check you AASA is well made as per apple policies.
Check you don’t have multiple AASA. One in hidden .well known directory and one outside on root. You have to debug all these things. There might be more to debug as it depends where your AASA is hosted and your server configurations etc.
May I ask one question? My app link is running fine, except that when my App is not installed on a mobile phone, I am expecting the app link to show a bar displaying link to the App Store to install my App, but it does not happen. What could be the problem? How can I troubleshoot the problem? Thank you
Hi
I think you are taking about banners which are shown in your website when app is not installed. Please check the apple doc where is given how to add a script to show a banner
cant we place aasa file in .well-known folder ?
Yes you can. You have 2 options. You can place the file at the root of your server or in the .well-known subdirectory.
@@rajanmaheshwari did that but still can't see AASA process initiated at my end through logs .Does it take some days to reflect the file from the day it is placed on our server?
@@shweta8677 No, it don't take time generally. Try deleting your app and then switch off the device and then again turning on. Re- install the app and see. I once experienced this as well. Also, I believe the server on which you are hosting the AASA is secure. (https)
Also as per apple, we can place the AASA in any of the locations
developer.apple.com/library/archive/documentation/General/Conceptual/AppSearch/UniversalLinks.html
@@rajanmaheshwari did this as well. Also not sure but can the provisioning profile create issue. I have checked the Automatically managed signing option in Xcode
issue fixed..actually the issue was with Xcode configuration..There are two entitlement files generated..one is appRelease and one is app so the associated domain entry was missing in app.entitlement file...by default when we configure Xcode it doesn't add entry in app.entitlement file ,we need to add it manually
itni bakvas krvalo simple si chiz ko itna bhada chada ke dikhane se time waste krva lo bs
hi @rajanmaheshwari
While going through swcutil file I’m seeing below:
User approval: unspecified
Site/Fmwk Approval: approved
But after tapping on the link when app is not installed it takes me to AppStore page of app but I installed build from TestFlight and there was no callback into any of the app delegate methods like open url or useractivity delegate.
Also is there any particular way to generate the deferred deep link for iOS.
Hoping to see ur response.
Hi Pooja. Thanks for checking out the video. There are certain things that still require investigation.
1. What deep deferred link mechanism are you using. (Appsflyer, Firebase, Branch, or something else). How are you generating a deferred deep link?
2. If you are using Firebase, have you enabled allow pasteboard as Firebase uses that for the dynamic deep link. Sometimes firebase dynamic method is not able to parse the link as the link was not properly URL encoded.
3. Is your dynamic links working in debug mode. Like clicking on the link without the app installed. It goes to Appstore and then you install it from Xcode. Check the openUrl method and debug the same.
Deep link can also fail if deferred deep link is not properly made.
Let me know if you have any questions.
hello, while doing the directory bruteforcing I got the path "./well-known/apple-app-site-association" after opening it I got some appID, and somepaths,. is this a Vulnerability ?? please reply
That is fine. This is your AASA file which informs about what paths will lead to deep links in your app. You can do the same approach for Google, Amazon domains etc and can see their AASA file.