If the author didn't create it you can look all you want, never to find it.
That's why nougat had a way to look it up. It was a list in app settings that would list all of the uri's for all of your installed apps. LMAO
So, if it was available before, I assume it would be available now. And I know it's available for the apps I'm trying to use because it will launch from other apps, which is how that works.
The supported links associations are related, but slightly different than the custom app URI Scheme.
App developers can register a custom scheme within their app which is a common feature in Android and iOS:
Starting with Android 6+, developers can also register an association with a domain, but they must also verify ownership of the domain:
In Android, both of these functionalities build on top of a concept called Intents which are a fundamental building block in navigating and running apps. Fully Kiosk Browser has a special way of handling these intents, but it's based on the Chrome Android Intents spec.
The difference between Chrome and Fully Kiosk Browser is that Chrome requires the app to specifically have registered a scheme. Whereas Fully Kiosk Browser parses the intent and then just tries to use it like a normal intent.
Okay...none of this is helpful at all. How do you find the custom scheme for an app? The option that I linked to is not available in Android Pie.
If you want to know if an app has a custom URL scheme registered, ask the app developer.
You can also try to read the app's manifest as that's where custom schemes are defined. It's not something that's exposed via normal user facing features in Android as it's typically more of a developer tool.
For example, you would look through the manifest looking at each activity to find an one with an intent-filter that has a data element with a custom android:scheme property.
<activity android:name="com.example.android.GizmosActivity" android:label="@string/title_gizmos" > <intent-filter android:label="@string/filter_view_http_gizmos"> <action android:name="android.intent.action.VIEW" /> <category android:name="android.intent.category.DEFAULT" /> <category android:name="android.intent.category.BROWSABLE" /> <!-- Accepts URIs that begin with "http://www.example.com/gizmos” --> <data android:scheme="http" android:host="www.example.com" android:pathPrefix="/gizmos" /> <!-- note that the leading "/" is required for pathPrefix--> </intent-filter> <intent-filter android:label="@string/filter_view_example_gizmos"> <action android:name="android.intent.action.VIEW" /> <category android:name="android.intent.category.DEFAULT" /> <category android:name="android.intent.category.BROWSABLE" /> <!-- Accepts URIs that begin with "example://gizmos” --> <data android:scheme="example" android:host="gizmos" /> </intent-filter> </activity>
Okay....so, as a practical matter then, no, this cannot be done then. Thanks.
Dunno there may be something useful here.
My thought. And forgive me I have not followed the whole thread.
Tasker on the device in question to trigger your app via intent. Then setup http endpoint in tasker you could then trigger from chrome?
Like he said you can, if the app developer has registered the intend.