Alexandru Gologan

Here's my test setup on Auth0 that works with the demo app (ofc this is just some generated keystore for debug): https://appauth-demo-ac8b0.web.app/.well-known/assetlinks.json ```json { "relation": ["delegate_permission/common.handle_all_urls"], "target": { "namespace": "android_app",...

It's not supposed to work, your signing key is not added to my debug environment: https://appauth-demo-ac8b0.web.app/.well-known/assetlinks.json I showed you this config as an example so you can figure out where...

Seems to be similar to #973 but unfortunately can't seem to reproduce the conditions you're describing.

@Diogo00dev thank you for the reference. Will keep this topic open for tracking purposes to see how the situation evolves until the final release.

Although not a typical configuration it should work fine. What you want in the end is `tools:node="merge"` which is also the default if you don't specify anything thus having both...

If it gets stuck at the redirect it's not an issue with the connection but with the way the integration works (or in this case doesn't). If that is the...

The issue is not with Custom Tabs or OAuth2.0/OIDC support but with support for **App Links**. Not all browsers implement App Links or honour them correctly, so when you redirecting...

The reference SO response by Iain is still correct. It's not very clear from what you've describe what the actual user workflow is. It might be you already have the...

Your description sounds reasonable. Recommend you use distinct redirectUris for each flavor and separate clients registered with your IdP for at least dev vs prod.

Not sure what you mean by digest for client credentials. Can you please link the OAuth2 or OpenID Connect section, or at least some public documentation?