Has anybody by change got app links working with custom url scheme? (The feature which identifies a link as "yours" and will not show a disambiguation dialog) -- but doesnt seem to work with custom schemes

app links?

But you don't need it for custom scheme, isn't it? Just define handling for custom scheme, and you will be the only app which can handle it

Well nobody is forbiding some 3rd party app to use my custom scheme as well, can it?

Yep, but does it really important? It's pretty clear why custom protocol is not supported, because it wouldn't be possible to validate your link, you can claim that some web domain belongs to you, and you validate it using a special file on this domain, but what about your custom protocol? Hi how would it be possible for the system proof that it's your domain on this protocol, imagine someone would claim that onion://google.com belongs to you, how would system validate it? There is no way to support all possible protocols What kind use case you have for it exactly? Or it's just theoretical

Yes it makes sense its impossible, Im just looking around. My issue is actually internal, login is via browser oauth, and have flavored apps depending on backend enviroment, and the redirectUri is same for all flavors so disambiguation dialog kicks in

Can you intercept the redirect before handling it? Set the package on the intent for the URI launch

You should use different path return url for every flavor, oauth allows to specify any custom redirect url Usage of your app id is unique enough

yes that makes most sense, thanks