Branch deeplink is opening playstore on Android 12 device if applicationIdSuffix is added

[Abhishek284]

On OS 12 and Above, if we have a build installed with applicationIdSuffix attached to our package name, branch deeplinks are unable to recognize the installed app and taking to playstore, but the same works fine in OS 11 and below. On OS 11 and below, the same links launch the installed app.

Branch Android lib version used: 5.1.0

[gdeluna-branch]

Hi Abhishek, we'll be investigating this soon.

[hazem3ly]

I faced the same issue and the fix was to change the android URI scheme on branch dashboard in configuration/general section to our applicationId, and by the way we are using applicationSuffix too

[Garguy]

I faced the same issue and the fix was to change the android URI scheme on branch dashboard in configuration/general section to our applicationId, and by the way we are using applicationSuffix too

So did you change the scheme inside Manifest also to be your applicationId?

I am now having the issue where the link only opens the URL provided in Default URL. Does not even try to open Play Store or app installed.

[LYevhen]

Copy answer from this issue
But be sure that You have putt all prefixed links to Your manifest file and deployed and got approved from google play store.
I believe that issue is because of it.
After release of Android API 31 there are some changes applied by google.
If You managing deep links on Your web page then You need to put:
[{
"relation": ["delegate_permission/common.handle_all_urls"],
"target": {
"namespace": "android_app",
"package_name": "com.example",
"sha256_cert_fingerprints":
["sha256_cert_fingerprints_REAL_VALUE"]
}
}]
in {your-domain}/.well-known/assetlinks.json (example.com/.well-known/assetlinks.json)
More is available here:
If You are using third party library for managing deep links, and configured everything on dashboard then first check what is returned by {your-domain}/.well-known/assetlinks.json (example.com/.well-known/assetlinks.json) - it should be the same as in example above in content for 'assetlinks.json'.
In other words If everything get broken after release of API 31 then You have to make sure that all links which are in Your AndroidManifest.xml in section and that application is published in playmarket and approved.
I had different config for dev env, and for prod, and links which was related on prod ( published to market ) did not include test links.
If links are associated with Your app and everything configured correct, You may go to Your app info ( long press on Your app on device) -> set as app default -> supported web addresses
there You should see Your links ( included in manifest file intent-filter section) and they should be enabled and You have to NOT have control ( toggle ) opposite to link, if You don't see any links or there is a toggle and it is turned off then something is wrong from steps above.
appInfo -> set as app default -> Open supported links ( toggle should be on )