Skip to content

Keep Discord sign-in in the web view instead of handing it to the Discord app - #156

Merged
itz4blitz merged 1 commit into
mainfrom
fix/discord-app-handoff
Nov 3, 2026
Merged

itz4blitz merged 1 commit into
mainfrom
fix/discord-app-handoff

Conversation

@itz4blitz

Copy link
Copy Markdown
Collaborator

What

On Android, Discord sign-in could hand off to the installed Discord app. Allowed navigations returned false from shouldOverrideUrlLoading, so the WebView passed non-web URLs (discord://, intent://) to whichever app claims them. The login finished in the Discord app and tinyclient never read the token.

Change

  • Only http, https, about, blob, data load in the sign-in view. Other schemes are dropped and logged.
  • Each allowed navigation logs its host (sign-in navigation: <host>) for logcat.

Testing

  • javac against android-36 compiles WebSignInActivity.java.
  • Not yet run on a device. Discord sign-in on a real phone is the check.

🤖 Generated with Claude Code

…cord app

On Android, a sign-in page navigation that the web view is allowed to load was
returned as "not handled", which lets the WebView pass it to whichever app
claims it. A discord:// or intent:// page therefore opened the installed Discord
app, which finished the login there, and tinyclient never read the token.

Only web pages (and about, blob, data) load in the sign-in view now. Any other
scheme is dropped and logged. Each allowed navigation logs its host, so a
handoff that comes from a plain https link shows up in logcat too.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
@itz4blitz
itz4blitz merged commit d49640a into main Nov 3, 2026
6 checks passed
@itz4blitz
itz4blitz deleted the fix/discord-app-handoff branch November 3, 2026 17:05
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