I am trying to redirect the user to the installed app when visiting www.example.com/success as well as show a banner when visiting the homepage www.example.com.
With my current implantation the url DOES NOT redirect and open the app and neither does the website display a banner.
I am following the documentation found here https://developer.apple.com/documentation/safariservices/supporting_associated_domains
My website is a simple create-react-app with a homepage hosted with Firebase.
I have done the following:
Add Associated Domains to Signing and Capabilities - applinks:website.com/success
Add apple-app-site-association file to /public/
Amend firebase.json file
Link to files in index.html
What I am using to validate:
https://branch.io/resources/aasa-validator/
https://search.developer.apple.com/appsearch-validation-tool
Testing by adding www.example.com/success link to notes and opening, It always opens in safari. I Have also tried reinstalling the app and restarting the phone.
Apple API Validation
I have uploaded a new app version with associated domains to the store
Branch.io
{
"applinks": {
"apps": [],
"details": []
}
}
When visiting www.example.com/apple-app-site-association
{ "activitycontinuation": { "apps": [ "team.com.example.com" ] },
"applinks": { "apps": [], "details": [ { "appID":
"team.com.example.com", "paths": [ "/", "/", "/success", "/success/",] }, "webcredentials": { "apps": [
"team.com.example.com" ] } }
apple-app-site-association
{
"activitycontinuation": {
"apps": [
"team.com.example.com"
]
},
"applinks": {
"apps": [],
"details": [
{
"appID": "team.com.example.com",
"paths": [
"/",
"/*",
"/success",
"/success/*",
]
},
]
},
"webcredentials": {
"apps": [
"team.com.example.com"
]
}
}
Index.html
<link rel="apple-app-site-association file" href="%PUBLIC_URL%/apple-app-site-association">
<link rel="apple-app-site-association file" href="/apple-app-site-association">
<meta name="App" content="app-id=XXX, app-argument=https://apps.apple.com/US/app/APP/idXXX, affiliate- data=optionalAffiliateData">
Firebase.json
{
"hosting": {
"public": "public",
"headers": [
{
"source": "/apple-app-site-association",
"headers": [
{
"key": "Content-Type",
"value": "application/json"
}
]
}
],
"appAssociation": "NONE"
}
}
Device Console
When installing the app I monitor the device console in Xcode looking through swdc process logs for anything related to associated domains or requests. Here's some I found;
Error getting enterprise-managed associated domains data. If this
device is not enterprise-managed, this is normal: Error
Domain=SWCErrorDomain Code=1701 "Failed to get associated domain data
from ManagedConfiguration framework."
UserInfo={NSDebugDescription=Failed to get associated domain data from
ManagedConfiguration framework., Line=298, Function=}
Entry { s = applinks, a = , d = au….ub….com, ua = unspecified,
sa = approved } needs its JSON updated because the app PI changed
https://developer.apple.com/library/archive/qa/qa1916/_index.html
First at your device logs and your JSON format it seems your should be following the example shown here: https://developer.apple.com/documentation/safariservices/supporting_associated_domains
In your logs it may shows logs from other apps who also have the outdated API format. However this should not be so much of an issue.
{
"applinks": {
"details": [
{
"appIDs": [ "ABCDE12345.com.example.app", "ABCDE12345.com.example.app2" ],
"components": [
{
"#": "no_universal_links",
"exclude": true,
"comment": "Matches any URL whose fragment equals no_universal_links and instructs the system not to open it as a universal link"
},
{
"/": "/buy/*",
"comment": "Matches any URL whose path starts with /buy/"
},
{
"/": "/help/website/*",
"exclude": true,
"comment": "Matches any URL whose path starts with /help/website/ and instructs the system not to open it as a universal link"
},
{
"/": "/help/*",
"?": { "articleNumber": "????" },
"comment": "Matches any URL whose path starts with /help/ and which has a query item with name 'articleNumber' and a value of exactly 4 characters"
}
]
}
]
},
"webcredentials": {
"apps": [ "ABCDE12345.com.example.app" ]
},
"appclips": {
"apps": ["ABCED12345.com.example.MyApp.Clip"]
}
}
Secondly following the steps in Apple's troubleshooting and your problem I am guessing your problem might be Step 7
Your app returned false from one of the following
UIApplicationDelegate protocol methods:
application(:continueUserActivity:restorationHandler:),
application(:willFinishLaunchingWithOptions:),
application(_:didFInishLaunchingWithOptions:).
This can happen if you
parsed the URL that is passed into these methods, and you implemented
logic to determine that your app can not use this URL.
You have not posted how you handle the URL. You need to implement the UIUserActivityRestoring method as suggested in the other answer for it to work. Here is a SwiftUI version
ContentView()
.onContinueUserActivity(NSUserActivityTypeBrowsingWeb) { userActivity in
print("Continue activity \(userActivity)")
guard let url = userActivity.webpageURL else {
return
}
print("User wants to open URL: \(url)")
// TODO same handling as done in onOpenURL()
}
Also add
.onOpenURL { url in
print("URL OPENED")
print(url) // parse the url to get someAction to determine what the app needs do
if url.relativeString == "example://success" {
}
}
https://developer.apple.com/library/archive/qa/qa1916/_index.html
There needs to be an appID in the apple-app-site-association:
{
"applinks": {
"apps": [],
"details": [
{
"appID": "XXXXXXXXXX.com.example.UniveralLinks",
"paths": ["*"]
}
]
}
}
The applinks tag determines which apps are associated with the web site. Leave the apps value as an empty array. Inside the details tag is an array of dictionaries for linking appIDs and URL paths. For simplicity, you use the * wildcard character to associate all of this web site’s links with the UniversalLinks app. You can limit the paths value to specific folders or file names.
The appID consists of your team ID combined with the app’s bundle ID, but you’ll need to use the identifier for your own account.
Apple assigned you a team ID when you created your Apple developer account. You can find it in the Apple developer center. Log into the web site, click on Membership, then look for Team ID in the Membership Information section.
Now you have the apple-app-site-association it must be uploaded to the web server.
You must have “write access” to the web site to do this. Be sure you set up the apple-app-site-association file correctly (either at the root or in .well-known/ on your web server, and no redirects).
You'll also have to add the appropriate entitlements for universal linking to the iOS app.
If you're using Xcode:
Select the project.
Select the target.
Select the Capabilities tab.
Scroll to and turn ON Associated Domains.
Then you can add e.g. applinks:www.mywebsite.in under `Capabilities -> Associated Domains.
Or in your entitlements file, you can add something like the following:
<key>com.apple.developer.associated-domains</key>
<array>
...
<string>applinks:www.mywebsite.in</string>
...
</array>
Handling Universal Links:
Now that the app and the web site are officially aware of each other, all the app needs is code to handle the link when it’s called.
func application(
_ application: UIApplication,
continue userActivity: NSUserActivity,
restorationHandler: #escaping ([UIUserActivityRestoring]?
) -> Void) -> Bool {
// 1
guard userActivity.activityType == NSUserActivityTypeBrowsingWeb,
let url = userActivity.webpageURL,
let components = URLComponents(url: url, resolvingAgainstBaseURL: true) else {
return false
}
// 2 // dig out component for deepLinking reference.
if let component = ItemHandler.sharedInstance.items
.filter({ $0.path == components.path}).first {
//handle navigation to page indicated by component
return true
}
// 3
if let webpageUrl = URL(string: "http://universal-links-final.example.com") {
application.open(webpageUrl)
return false
}
return false
}
iOS calls this method whenever the user taps a universal link related to the app. Here’s what each step does:
First, you verify that the passed-in userActivity has expected characteristics. Ultimately, you want to get the path component for the activity. Otherwise, you return false to indicate that the app can’t handle the activity.
Using the path, you look for a known view controller that matches it. If you find one, you present the view controller for it and return true.
If you can’t find a view controller that matches the path, you instruct the application to open the URL, which will use the default system app instead — most likely Safari. You also return false here to indicate that the app can’t handle this user activity.
Related
My team and I are actively developing an app with an associated app clip, however, we are unable to test the app clip's launch on any device other than the simulator due to receiving the error: "This app clip is not currently available in your country or region" A local experience has been registered, the domain has been properly associated with the apple-app-site-association file, the experience has been registered on app store connect, and the app clip can be launched normally. (Without the advanced url invocation). If anyone could know a reason this could be happening, it would be greatly appreciated! We have tried just about everything at the moment.
Association file:
{
"applinks": {
"details": [
{
"appIDs": [ "GROUPID.APPID"],
"components": [
{
"/": "/*",
"comment": "Matches any URL with a path that starts with /."
}
]
}
]
},
"appclips": {
"apps": ["GROUPID.APPID.Clip"]
}
}
Add line "paths": ["*"] after "appIDs": [ "GROUPID.APPID"] and also make sure you Added
Associated Domins in both Appclip targets and main app targets
Domins:
appclips:appcliptest.com
applinks:appcliptest.com
{
"applinks": {
"details": [
{
"appIDs": [ "GROUPID.APPID"],
"paths":["*"],
"components": [
{
"/": "/*",
"comment": "Matches any URL with a path that starts with /."
}
]
}
]
},
"appclips": {
"apps": ["GROUPID.APPID.Clip"]
}
}
I am trying to implement a mechanism that allows me to open my application for all paths that contains the last path same.
Actually I am confuse what if should be '/connect-premium.html' or '//connect-premium.html'
"/folder1/connect-premium.html"
"/folder1/folder2/connect-premium.html"
"/folder1/folder2/....../folderN/connect-premium.html"
https:///.well-known/apple-app-site-association
{
"applinks": {
"apps": [],
"details": [
{
"appID": "<Team ID>.<Bundle Identifier>",
"paths": [
"*/connect-premium.html"
]
}
]
}
}
I have implemented deep linking for Android and iOS, below method works perfectly with android but I am facing problem with iOS.
It navigates to the page of app link but comes back to main screen automatically.
Below is the implementation of my method. I have followed everything from MSDN for deep linking.
protected override async void OnAppLinkRequestReceived(Uri uri)
{
string appDomain = "https://" + "mydomain.com".ToLowerInvariant() + "/";
if (!uri.ToString().ToLowerInvariant().StartsWith(appDomain, StringComparison.Ordinal))
return;
string pageUrl = uri.ToString().Replace(appDomain, string.Empty).Trim();
var parts = pageUrl.Split('?');
string page = parts[0];
string pageParameter = parts[1].Replace("id=", string.Empty);
var formsPage = Activator.CreateInstance(Type.GetType(page));
var jobItemPage = formsPage as JobDetail;
if (jobItemPage != null)
{
jobItemPage.BindingContext = new JobDetailViewModel(int.Parse(pageParameter));
await MainPage.Navigation.PushAsync(formsPage as Page);
}
base.OnAppLinkRequestReceived(uri);
}
Below is my apple-app-site-association file:
{
"applinks": {
"apps": [],
"details": [
{
"appID": "MyTeamIdPrefix.com.deepLinking",
"paths": [ "*" ]
}
]
}
}
Make sure your Associated Domains in Apple Developer is enabled.
Created apple-app-site-association. And there is no error in the content.
Enable Associated Domain and add the domain of the website in the Entitlements.plist file.
{
"applinks": {
"apps": [],
"details": [
{
"appID": "47BSW6D45T.com.acno.AppBundleId",
"paths": [
"/?v=*", "/v=*", "/*v=*"
]
}
]
}
}
I tried paths that is write in paths Array but did not open my url from message or mail or from safari
The older paths element in the site association file that is used by iOS 12 and earlier only examines the path of the url.
From the documentation:
Note that only the path component of the URL is used for comparison. Other components, such as the query string or fragment identifier, are ignored.
If you only want your app to handle urls with a specific query string then you will need to check the query string in the URL once your app receives it.
If the query string doesn't meet your requirements then you can pass the URL to openURL to have it opened in Safari.
In iOS 13, the components key in your site association file can specify a query string match.
{
"applinks": {
"apps": [],
"details": [
{
"appID": "47BSW6D45T.com.acno.AppBundleId",
"paths": [
"*"
],
"appIDs": ["47BSW6D45T.com.acno.AppBundleId"],
"components":[
{
"/": "*",
"?": { "v": "*" },
"comment": "Matches any URL whose path starts with / and which has a query item with name 'v'"
}
}
]
}
}
I'm creating an iOS application using trigger IO, and I would like to add my application's shortcut icon to the list of available editors for certain file types. Like in this article, can this be done using trigger io?
My app inside iMessage UIActivityViewController
I've added the build_steps.json to the ios custom module. I can't get the correct syntax. I get an error from the forge build procress.
[ ERROR] 2013-11-29 22:29:56,654 -- set_in_info_plist() got an unexpected keyword argument 'UTImportedTypeDeclarations'
Here is my build_steps.json:
[
{
"do": {
"set_in_info_plist": {
"UTImportedTypeDeclarations":
[
{
"UTTypeConformsTo":
[
"public.image"
],
"UTTypeIdentifier": "public.png",
"UTTypeTagSpecification":
{
"com.apple.ostype": "PNG",
"public.filename-extension":
[
"png"
],
"public.mime-type": "image/png"
}
},
{
"UTTypeConformsTo":
[
"public.image"
],
"UTTypeIdentifier": "public.jpeg",
"UTTypeTagSpecification":
{
"com.apple.ostype": "JPEG",
"public.filename-extension":
[
"jpg"
],
"public.mime-type": "image/jpeg"
}
}
]
}
}
}
]
Can anyone tell me what is wrong with this file?
This isn't possible with Trigger's built in functionality, but should be possible by writing your own native module.
See https://trigger.io/docs/current/api/native_modules/index.html and in particular https://trigger.io/docs/current/api/native_modules/native_build_steps.html#set_in_info_plist for updating the Info.plist for an app.