Changes needed when targetting SDK 30+
See original GitHub issueThe new package visibility changes in Android 11 means that all of the queryIntentActivities()
call BrowserSelector.java is broken.
As per the docs, the following should be added to your app’s manifest when targeting SDK 30 and above:
<manifest>
<application>
<blah />
</application>
<queries>
<intent>
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.BROWSABLE" />
<data android:scheme="https" />
</intent>
<intent>
<action android:name="android.support.customtabs.action.CustomTabsService" />
</intent>
</queries>
</manifest>
Issue Analytics
- State:
- Created 3 years ago
- Reactions:17
- Comments:10
Top Results From Across the Web
Behavior changes: Apps targeting Android 11
The following behavior changes apply exclusively to apps that are targeting Android 11 or higher. If your app sets targetSdkVersion to 30 ,...
Read more >How to up targetSdkVersion 26 to targetSdkVersion 30?
there are lots of information on what have changed in each target sdk bump. You need to look at your code and apply...
Read more >New Android App Bundle and target API level requirements in ...
From November 2021, updates to existing apps will be required to target API level 30 or above and adjust for behavioral changes in...
Read more >Targeting Android SDK 30 — Engineering Blog - Wealthfront
Now, with our migration to SDK 30 complete, we'd like to detail the changes our team made. This is not meant to be...
Read more >Update your target Android API level by November 1 - Ionic Blog
For new updates to an existing app, a target API level of 31 is required. App bundles or APK's targeting a level of...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@peshkira we have modified that fix to be part of the library manifest thus including it via the manifest merge process. Once we get some time we’ll publish an official release including this fix.
@chrisbanes Thank you for reporting this.
Just tested this on sdk31 and haven’t seen the issue mentioned by the OP. Please open a new issue describing the problem you’re encountering.
Locking this issue to avoid further comments without proper context.