Android 12 App links not working

Samsung Internet
26

I tried using the intent pattern for the same but still, the redirection to the app doesn’t happen doesn’t happen!
Chrome, Mozilla, edge, brave, etc… do seem to work but not Samsung internet.
Can you please provide support please?

intent://mydomain.com/auth/callback?auth_signature=xXpD21S2fdgadf3#Intent;scheme=https;package=com.myapp.com;end

<intent-filter android:autoVerify="true">
                <action android:name="android.intent.action.VIEW" />

                <category android:name="android.intent.category.DEFAULT" />
                <category android:name="android.intent.category.BROWSABLE" />

                <data android:scheme="https" />
                <data android:host="mydomain.com" />
                <data android:pathPattern="/auth/callback.*" />
            </intent-filter>
27

Hello,

Welcome to the Samsung Developers Forums!

We are sorry to know that. Can you please create a support ticket here so we can address it better?

Sincerely,
Samiul Hossain
Samsung Developers Forums

28

I have already done that. The ticket number is #47598.

Would be great if you could take a look at it at the earliest as the authentication stands interrupted due to this :frowning:!

1 Like
29

Hello,

We have forwarded your issue to the Samsung Internet team. Please wait while they get back to us with your request.

Sincerely,
Samiul Hossain
Samsung Developer Relations

30

There is a problem with the system. I have found out what it is. This might not just be with Samsung mobiles but rather with mobile devices running Android 13 and higher. We can navigate to the app’s settings and enable the supported web links in it. But this is not user-friendly, so we must follow the Android’s deep link article and implement it as such(assetslinks.json/ intent filters/ app’s compatibility). And worth mentioning it doesn’t work with wildcard links :frowning:

31

After few days of trial and error with Samsung mobiles, finally we managed to get the Android App Link works, basically you need to make sure your scheme/host defined in manifest file able to get auto verified.

Below is the manifest sample that works for us:

<intent-filter android:autoVerify="true">
    <action android:name="android.intent.action.VIEW"/>
    <data android:scheme="https"/>
    <data android:host="example.com"/>
    <category android:name="android.intent.category.BROWSABLE"/>
    <category android:name="android.intent.category.DEFAULT"/>
</intent-filter>

And some tips from our trial and errors:

  • use separate tag for android:scheme and android:host, do not use both value into a single tag
  • do not use wildcard (*) for host
  • do not use any path (android:path)
  • use android:autoVerify="true" on intent filter.
  • use only android:scheme="https", remove other non “https” scheme from this intent filter.
  • make sure assetlinks.json file for all the defined host is accessible (https://example.com/.well-known/assetlinks.json)
  • make sure all fingerprints in assetlinks.json file is correct (use fingerprint from play console if your app is signed by play console integrity)

Before we got things right, we always see a warning on Google Play Console Deep Links page, but couldn’t identify what’s the problem. Now everything works good, and no more warning from Deep Links.

Hope it helps.

3 Likes