Skip to content

Open in-app browser links in a Custom Tab instead of the browser chooser when no default browser is set - #1630

Merged
prof18 merged 1 commit into
mainfrom
fix/bug-inapp-browser-chooser
Nov 6, 2026
Merged

prof18 merged 1 commit into
mainfrom
fix/bug-inapp-browser-chooser

Conversation

@prof18

@prof18 prof18 commented Nov 6, 2026

Copy link
Copy Markdown
Owner

With the in-app browser selected, links (e.g. the source links inside Google News feed content) launched a Custom Tab without a target package, so on devices with several browsers and no default one Android showed the "Open with" chooser. The Custom Tab is now pinned to a Custom Tabs provider only when the system has no default handler for the link, leaving default-browser and verified app-link routing unchanged. Reproduced and verified on an API 36 emulator with two browsers and no default (chooser before, direct Custom Tab after), covered by InAppBrowserPackageTest; a Maestro flow isn't feasible because it needs a device with no default browser.

@prof18
prof18 enabled auto-merge (rebase) November 6, 2026 11:36
@prof18
prof18 merged commit d119a68 into main Nov 6, 2026
7 checks passed
@prof18
prof18 deleted the fix/bug-inapp-browser-chooser branch November 6, 2026 11:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant