Skip to content

Modify AndroidManifest.xml to address package visibility issue in Android 11 #107

@jpatdu-credovita

Description

@jpatdu-credovita

With the release of Android 11 comes new handling of package visibility

I'm suspecting that because of this, my app on emulated Android 10 works fine; But on my phone with Android 11 the auth activity thinks that there are no browsers installed, thus presenting an error that (incorrectly) states that my phone does not have a web browser to launch the Auth0 website for logging in.

Particularly, I see this on my Logcat:
AppsFilter: interaction: PackageSetting{c742ef3 com.mica.drugstore/10544} -> PackageSetting{115f6c5 com.android.chrome/10187} BLOCKED

What ultimately fixed this was adding the QUERY_ALL_PACKAGES permission in my AndroidManifest.xml, as so:
<uses-permission android:name="android.permission.QUERY_ALL_PACKAGES"/>

Moving forward, I'm practically clueless as to native Android development, so I'm not quite sure how this can be implemented in the project — could a simple PR to the README asking users to add the aforementioned permission alongside the RedirectActivity be enough? Or could this be implemented in code? Or — could the problem be on entirely on my end?

Thanks

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions