bug: Custom OAuth login succeeds server-side every time but app loops back to login screen (iOS, 4.75.0)
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 52/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Tranquilo
- Stack tecnológico
- ios, react-native, typescript
- Área
- authentication, mobile
Línea de trabajo
Empieza siguiendo el flujo móvil de Custom OAuth a través de ASWebAuthenticationSession/Chrome Custom Tabs y la login saga, comparándolo con la corrección de cancelación de #7340 y la reestructuración de #6987/#7419. Usa el POST /api/v1/login exitoso reportado como límite de inspección; terminado significa que una respuesta OAuth exitosa hace que la aplicación avance más allá de la pantalla de inicio de sesión sin reiniciar el handshake.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Describe the bug
Logging in via a Custom OAuth provider (self-hosted Keycloak, standard OIDC) on the mobile app succeeds completely on the server side every single time, but the app never leaves the login screen — it silently re-initiates the entire OAuth handshake every ~15-20 seconds in an infinite loop. Web login against the exact same Custom OAuth provider/server works correctly on the first try.
Environment
- App version: 4.75.0
- Platform: iOS (native app, "RC Mobile")
- Server version: Rocket.Chat 8.6.1
- Auth method: Custom OAuth pointed at a self-hosted Keycloak instance (standard OIDC —
/auth,/token,/userinfoendpoints) - Login Style: Tried both
PopupandRedirectin Admin → OAuth → (custom provider) — no change in mobile behavior either way - 2FA: Disabled account-wide for testing — no change in behavior
Steps to reproduce
- Configure a Custom OAuth provider against a standard OIDC/Keycloak server.
- Open the RC Mobile app (iOS), tap the custom OAuth login button.
- Authenticate against the identity provider (Keycloak login page).
- Observe: the auth popup/browser session closes with no visible error, but the app stays on the login screen.
- Wait ~15-20 seconds without doing anything — a brand new OAuth handshake (fresh authorization code) starts automatically, completes silently (no re-prompt, since the IdP still has an active session), and the app still doesn't log in. This repeats indefinitely.
What I verified server-side (ruling out server/IdP/proxy causes)
Traced the full request chain end-to-end across three independent login attempts, all with identical results:
GET https://sso.example.com/realms/<realm>/protocol/openid-connect/auth?client_id=<id>&redirect_uri=https%3A%2F%2Fchat.example.com%2F_oauth%2F<provider>&response_type=code&state=<state>&scope=openid
→ Keycloak returns302immediately (existing IdP session, no interactive prompt needed after the first attempt).- RocketChat's server exchanges the code:
POST https://sso.example.com/realms/<realm>/protocol/openid-connect/token→ succeeds. GET https://sso.example.com/realms/<realm>/protocol/openid-connect/userinfo→ succeeds, returns the full identity (email, name, sub, etc.).- RocketChat's
CustomOAuthlogs"Identity response"with the correct user identity. - RocketChat's login-validation callbacks fire cleanly, in order, with no exception:
afterValidateNewOAuthUser→onValidateLogin→afterValidateLogin. - The app's own REST call —
POST /api/v1/loginwithuserAgent: RC Mobile; ios ...and the OAuth credential in the body — returns HTTP 200.
This full sequence (steps 1-6) completed successfully three times in a row across separate login attempts, each with its own fresh authorization code, each getting a clean 200 on /api/v1/login. There is no error, rejection, or exception anywhere in the server-side chain on any attempt. Despite that, the app immediately restarts the same sequence again ~15-20 seconds later, and never transitions out of the login screen.
Decoded state parameter from the request (values redacted, structure intact):
{
"loginStyle": "redirect",
"credentialToken": "<redacted>",
"isCordova": true,
"redirectUrl": "rocketchat://auth"
}
Note loginStyle is redirect regardless of what the server's Admin → OAuth → Login Style setting is configured to (tried both Popup and Redirect server-side with no change in this value or in mobile behavior) — the mobile app appears to always request redirect style for Custom OAuth, independent of that server setting.
Possibly related
This looks like it could be the same underlying class of bug as #7333 (fixed by #7340: "don't cancel login saga on 2s timeout") — a race/cancellation between successful OAuth completion and the UI state advancing past the login screen — but resurfacing in the newer native-browser-session Custom OAuth flow introduced by #6987 / #7419 (which moved Custom OAuth to ASWebAuthenticationSession/Chrome Custom Tabs and explicitly forced redirect-style login, "activating existing (previously dormant) saga logic"). #7340's fix predates that rework, so it may not cover this newer code path.
Expected behavior
After a successful OAuth completion (confirmed server-side), the app should recognize the returned session and transition to the logged-in state, rather than silently discarding it and re-initiating the OAuth flow.
Additional notes
- Uninstalling and reinstalling the app does not change the behavior.
- Force-quitting and reopening the app does not change the behavior.
- Happy to provide more detail (redacted server logs, HAR-equivalent request traces) on request — omitted here since they contain internal hostnames/identifiers.
- Lenguaje dominante
- TypeScript
- Estrellas
- 2.4k
- Forks
- 1.5k
- Merge medio
- 1 d 15 h
- PR fusionados (30 d)
- 29
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de RocketChat/Rocket.Chat.ReactNative
-
[IMPROVEMENT] Remove redundant `await` on synchronous `userPreferences.getBool` in `getUsersPresence`Posiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertotype: feature
Dificultad 1/5 Menos de una hora Aptitud para principiantes 92/100
RocketChat/Rocket.Chat.ReactNative#7737 ·
Los mantenedores suelen responder en 1 día
-
UIKit modal: a viewSubmit response with no `type` field fails to close the modal on mobile (regression from #7057)Posiblemente ocupada @erikurt9 la tomó hace 106 días. Abiertotype: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
RocketChat/Rocket.Chat.ReactNative#7503 · 3 comentarios · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
type: bug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 86/100
RocketChat/Rocket.Chat.ReactNative#7437 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
✅ tests 👷 ci type: feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
RocketChat/Rocket.Chat.ReactNative#7247 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug: goRoom navigates to broken RoomView after failed DM creation from searchPosiblemente ocupada @deepak0x la tomó hace 216 días. Abiertotype: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
RocketChat/Rocket.Chat.ReactNative#7098 ·
Los mantenedores suelen responder en 1 día
Todos los issues de RocketChat/Rocket.Chat.ReactNative
Issues similares
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
langchain-ai/langchainjs#12239 ·
Los mantenedores suelen responder en 1 día
-
Board view: the Monitoring column is always empty because compact issue rows drop displayStatusAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
paperclipai/paperclip#21837 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
code-yeongyu/senpi#6813 ·
Los mantenedores suelen responder en 1 día
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Dificultad 1/5 Menos de una hora Aptitud para principiantes 93/100
lingdojo/kana-dojo#34169 · 1 comentario · 5 reacciones ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100