android - Multiple market handlers cause app not to be found -

android - Multiple market handlers cause app not to be found -

google suggests way link google play store is:

market://details?id=<package_name> if in application, , http://play.google.com/store/apps/details?id=<package_name> if on webpage.

when followed strategy, got toast of "no such app found", though google play store had app looking for.

this turned out caused competition of 2 market handlers: f-droid (open source marketplace) , google play store. found there multiple looking @ bundle manager intent resolvers.

i ever want apps in google play store linked app. there way forcefulness app respond market://[...] link?

other strategies suggest attempting 1 approach, , if fails, trying http://[...] link. (the linked solution failed me, no exception thrown.)

what go wrong if link via http:// method? i.e., skip market:// link, , utilize http:// straight in app. decision come haunt me later?

i'm not linking open source apps, i'm linking google play store ones

no, trying open uri action_view intent. in principle, user welcome handle request want, can open pdf whatever app want. 1 of few places in android think justified seek forcefulness issue , steer user particular app , away whatever might choose.

i ever want apps in google play store linked app. there way forcefulness app respond market://[...] link?

if 1 calling startactivity() uri, wrap intent in intent.createchooser(). forcefulness chooser dialog appear, avoiding default, if there more 1 activity matching intent. safest , stable approach, not depend on details of play store itself.

you phone call setcomponent() on intent , provide componentname theoretically points desired activity. that's 1 google refactoring away breaking.

you can seek see if setpackage() limit intent resolution desired app. 1 time again, if google decides switch different bundle entry point play store, have adapt. , i'm not sure if setpackage() honored in scenario.

other strategies suggest attempting 1 approach, , if fails, trying http://[...] link. (the linked solution failed me, no exception thrown.)

yes, because problem isn't there's no match, there multiple matches, , selection made instead of 1 want.

what go wrong if link via http:// method? i.e., skip market:// link, , utilize http:// straight in app.

this doesn't solve problem, insofar there other apps handle intent, web browsers.

android google-play