AppLink | AppLink allows you open some link

After the build has failed go to AndroidManifest.xml and in the bottom click merged manifest see which activities which have intent-filter but don't have exported=true attribute. Or you can just get the activities which are giving error.

Add these activities to your App manifest with android:exported="true" and app tools:node="merge" this will add exported attribute to the activities giving error.

Example:

The prefix adb shell indicates that the command is executed on Android side, thus unless the adb shell command itself fails the platform-tools have no impact on the command.

A little bit up on the linked page you can read "Starting in Android 12". Most likely adb shell pm verify-app-links is also limited to devices with Android 12 or higher.

I guess no one have interest in that, so i will answer myself after finding out the way, maybe it will be useful to someone else later.

The association file have to be present on both subdomain.domain.com and domain.com for "applinks:*.subdomain.domain.com" to be working.

If you want to limit to "applinks:a.subdomain.domain.com" and "applinks:b.subdomain.domain.com", the file have to ALSO be present in a.subdomain.domain.com and b.subdomain.domain.com or any other subdomain you will explicitly specify in the app entitlements.

Very poorly documented by apple for such an important feature.

This looks fine.

If you want to call getLink() from your App Delegate, you'll need to import the Auto-generated Swift Bridging Header File that Xcode creates when you compile your code. This will allow the Objective-c AppDelegate.m file to find your exposed swift code.

#import will allow your Swift to be exposed to the AppDelegate, and you already have marked the class and functions @objc so they will be visible.

Then you just need to either create a singleton or shared instance of your AppLinkModule (React Native Modules are all run statically) or you need to instantiate your module class.

Once you've done so, you can call this function in the AppDelegate like so:

[[[AppLinkModule ] shared ] getLink];

Instead of using a variable for the ASSOCIATED_DOMAIN value, consider specifying a separate entitlements file for each of the schemes. In the relevant xcconfig file, this can be done by setting:

Looks like you're trying to download an old version of the facebook adapter (as mentioned in the conment - bintray is shutting down) IronSource latest integration shows that the artificat is now downloaded from a new location: https://developers.is.com/ironsource-mobile/android/mediation-networks-android/#step-2

Replace your current integration and follow the unity integration guide as explained here: https://developers.is.com/ironsource-mobile/unity/mediation-networks-unity/#step-1

It will resolve you're conflict.

I'm sure you already visit the following link: https://developer.android.com/studio/write/app-link-indexing

Just a little bit improve your manifest to clean the code

iOS uses a different mechanism for dealing with applinks than it does for custom app URL schemes, so it is likely that there is a race condition here -where start() is being called before the URL is provided to the app.

Try implementing the com.codename1.system.URLCallback interface in your main lifecycle class and implement the shouldApplicationHandleURL method. This should be called when an applink is processed.

Ok, I did find the issue and fix... It's not that hard actually and I bumped into it accidentally...

It seems that Apple does a really bad job in parsing HTML, in particular the href attribute of a link. While I could not find any other client that behaves the same, it seems that if you don't put the scheme (http or https) in front of the url (so instead of https://google.com I was using just google.com) which you provide to the href attribute, then Apple makes something of it's own out of it: x-webdoc://30E09690-F388-4ED2-BB46-14DC829B974C/google.com. I could spot this on the Apple Mail app, however on the iPhone where I was having the issue it was not even recognised as a link, so the behaviour seems to be a little different between their own apps.

In the end it was my mistake for not putting https:// in front of my auto generated URI's. However I do think Apple does a poor job here in building the link HTML tag.