[GH-ISSUE #2903] Android login hangs on "generating sign in code..." when browser is Firefox #9029

Open
opened 2026-04-30 05:16:41 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @Plecebo on GitHub (Apr 26, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2903

Describe the Bug

After completing OIDC authorization in the browser, the app stays on "generating sign in code..." indefinitely. The success page fires an Android deep link via window.location.href = "intent://auth-success#Intent;scheme=pangolin;package=net.pangolin.Pangolin;end" — but Firefox on Android silently ignores intent:// URIs (this scheme is Chrome-only). The app never receives the callback and never polls for the session token.
Server side completes correctly: deviceWebAuthCodes shows verified=1 with the correct userId populated. Zero network traffic from the device after the OIDC redirect — the app is simply never signaled.

Environment

  • Pangolin: 1.17.1
  • Android app: latest (Play Store)
  • Browser: Firefox for Android (reproduced); Chrome for Android (works)

To Reproduce

  1. Open the Pangolin Android app → tap Sign In
  2. When the browser opens, complete OIDC authorization (Authentik)
  3. Browser reaches the success page
  4. App remains on "generating sign in code..." spinner indefinitely

Expected Behavior

App receives the deep link callback, polls /api/v1/auth/device-web-auth/poll/, and completes login.

Originally created by @Plecebo on GitHub (Apr 26, 2026). Original GitHub issue: https://github.com/fosrl/pangolin/issues/2903 ### Describe the Bug After completing OIDC authorization in the browser, the app stays on "generating sign in code..." indefinitely. The success page fires an Android deep link via window.location.href = "intent://auth-success#Intent;scheme=pangolin;package=net.pangolin.Pangolin;end" — but Firefox on Android silently ignores intent:// URIs (this scheme is Chrome-only). The app never receives the callback and never polls for the session token. Server side completes correctly: deviceWebAuthCodes shows verified=1 with the correct userId populated. Zero network traffic from the device after the OIDC redirect — the app is simply never signaled. ### Environment - Pangolin: 1.17.1 - Android app: latest (Play Store) - Browser: Firefox for Android (reproduced); Chrome for Android (works) ### To Reproduce 1. Open the Pangolin Android app → tap Sign In 2. When the browser opens, complete OIDC authorization (Authentik) 3. Browser reaches the success page 4. App remains on "generating sign in code..." spinner indefinitely ### Expected Behavior App receives the deep link callback, polls /api/v1/auth/device-web-auth/poll/<code>, and completes login.
Author
Owner

@qroac commented on GitHub (Apr 30, 2026):

Same for me.
Tested with OIDC authentication (keycloak) and local admin user

Smartphone: Samsung S21

Worked after switching default browser from firefox to chrome.

<!-- gh-comment-id:4350672464 --> @qroac commented on GitHub (Apr 30, 2026): Same for me. Tested with OIDC authentication (keycloak) and local admin user Smartphone: Samsung S21 Worked after switching default browser from firefox to chrome.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#9029