Fulguris icon indicating copy to clipboard operation
Fulguris copied to clipboard

GitHub inbox tap shows app launch selector

Open Slion opened this issue 2 months ago • 2 comments

Description

When not logged on GitHub tapping a GitHub link gives an app selector with only 3 browsers from the many installed on that device.

Environment

  • Device: HUAWEI Magic V2
  • OS: Android 15
  • Version: 1.11.0
  • WebView:

To reproduce

Steps to reproduce the behaviour:

  1. Search for GitHub on Google
  2. Click on the first link
  3. Browser selection dialog shows up

You can also reproduce this when being logged in GitHub and just tapping your inbox icon with app launch enabled.

You can also use adb: adb shell am start -a android.intent.action.VIEW -d "https://github.com/sponsors/Slion"

Mind you the following just works and launch the GitHub app proper: adb shell am start -a android.intent.action.VIEW -d "https://github.com/Slion/Fulguris"

So it really depends on the URL you pass to the GitHub app.

Expected behaviour

We should be able to handle that from Fulguris and not redirect to another browser.

Screenshots

Image

Additional context

Happens only when app launch domain settings resolves to yes.

Workaround

Disable app launch for github.com domain.

Slion avatar Nov 01 '25 08:11 Slion

This chooser is shown by the GitHub app much like we did our own browser selection activity. If you reset GitHub app and do not sign-in again, it does show its sign-in screen below the chooser. Testing on device without the GitHub app works just fine. Also adding debug logs to isSpecializedHandlerAvailable confirms we launch the GitHub app. Testing the GitHub login process from Chrome Beta works however it does launch the GitHub app as you tap the Sign-in button even though it's not noticeable, if you hit back Chrome sends itself to the background thinking it should go back to an app.

I wonder why the GitHub app reacts differently when Fulguris launches it and when Chrome launches it. It should not be able to tell from where the intent it coming I think. So maybe it does not like how we constructed our intent. We ought to check how Chrome construct its intents somehow.

Using Intent.EXTRA_REFERRER did not help.

Slion avatar Nov 02 '25 19:11 Slion

I reported that issue to GitHub: https://github.com/orgs/community/discussions/181332

Slion avatar Dec 06 '25 19:12 Slion