You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Android Security Alert: Another app on your phone may be trying to... #293
Using the SDK in a debug build in Android emulator, dropbox.AuthActivity errors out with a Security Alert "There might be more than one app trying to handle....".
I see that it is very similar to : #153 and the error is
With the advent of App Bundle, can the dropbox.AuthActivity declaration continue to be in a module's manifest or should it be in the base module's manifest? For some reason, when AuthActivity starts, it's finding 2 instances of it under my app's packagename.
Can you try restarting the emulator's OS, if you haven't already? While not typically necessary, in some cases we've heard that a restart is required for the system to reflect changes to these.
Thanks for checking that. I'm not sure off hand what may be causing this then, so we'll have to look into it. (It may be related to using an App Bundle, but I don't know if the SDK has been tested with that in particular. I believe it predates App Bundles.)
To help us reproduce this, would you be able to share am AndroidManifest.xml file(s) (or a sample project, if possible), that produces this issue? Thanks in advance!
Activity
vikrama commentedon Oct 30, 2020
With the advent of App Bundle, can the dropbox.AuthActivity declaration continue to be in a module's manifest or should it be in the base module's manifest? For some reason, when AuthActivity starts, it's finding 2 instances of it under my app's packagename.
greg-db commentedon Oct 30, 2020
Can you try restarting the emulator's OS, if you haven't already? While not typically necessary, in some cases we've heard that a restart is required for the system to reflect changes to these.
vikrama commentedon Nov 7, 2020
Yes, behavior continues after a cold start and even after restarting the OS.
greg-db commentedon Nov 9, 2020
Thanks for checking that. I'm not sure off hand what may be causing this then, so we'll have to look into it. (It may be related to using an App Bundle, but I don't know if the SDK has been tested with that in particular. I believe it predates App Bundles.)
To help us reproduce this, would you be able to share am AndroidManifest.xml file(s) (or a sample project, if possible), that produces this issue? Thanks in advance!
Sardarwaqas800 commentedon Dec 31, 2020
Clear all issue