Here scheme=https correspond to https: in the original URL, so if you want to convert a plain http: URL, this field should be scheme=http. The corresponding intent: link which opens it in the Google Drive app will be: intent:///document/d/1zSzDnV-90Ke3dzCCJ2CZ6iQ3JQ3F1hL1udGDqbNwwbY/edit?usp=sharing#Intent scheme=https action= category= category= package=.docs endĪ test link with this URI is on a separate page (it is not possible to make an actual link pointing to such URI here).Īppend intent parameters: #Intent scheme=https action= category= category= package=.docs end I have not been able to find proper documentation for the intent: URI format of course, the source code for the function which generates such URIs is available. There is another way to make a link which starts an Android app - use the intent: URI scheme. I tested Chrome, Dolphin, Firefox, Light Browser, Opera (including Classic and Mini), UC Browser, and all of them just opened the link internally instead of offering to pass it to the Google Drive app. And this actually works - when using the stock Android browser, attempting to open a link pointing to results in the chooser popup with the Google Drive app included in the list (together with all installed browsers) selecting Google Drive results in opening the document in the Google Drive editor, as you want.īut the problem is that such intercepted HTTP URLs work only in the stock Android browser - I have not been able to find any third-party browser which could show the app chooser when following such links. The Google Drive app does exactly this - it registers intent filters for, , and a bunch of similar URLs (including http: with the same host names). According to this answer on StackOverflow, intercepting http: or https: URLs is the proper way to start an app when opening a link from the Android browser. link for the document should work for you.
Using http: or https: links intercepted by an app There does not seem to be a good way to do what you want (at least according to my testing with Android 4.0.4 maybe the situation is different with other versions).
0 kommentar(er)
