Users getting logged out with "Unsuccessful Refresh Token exchange, reused refresh token detected"
Los mantenedores suelen responder en 1 día
@subhankarmaiti ya está trabajando en esto.
Desde el 16/12/2025.
- #1738 de @subhankarmaiti — fusionado
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Checklist
- The issue can be reproduced in the react-native-auth0 sample app (or N/A).
- I have looked into the Readme, Examples, and FAQ and have not found a suitable solution or answer.
- I have looked into the API documentation and have not found a suitable solution or answer.
- I have searched the issues and have not found a suitable solution or answer.
- I have searched the Auth0 Community forums and have not found a suitable solution or answer.
- I agree to the terms within the Auth0 Code of Conduct.
Description
Our usage of Auth0 is pretty simple. After the user has been logged in we just attach the access token to network calls and verify them server side.
const useApi = (): Api => {
const { getCredentials } = useAuth0()
const backend = axios.create({ baseURL: apiUri, timeout: 10000 })
backend.interceptors.request.use(
async config => {
const credentials = await getCredentials()
config.headers["Authorization"] = `Bearer ${credentials?.accessToken}`
return config
},
async error => {}
)
}
We have gotten user reports that they get error in title. Our understanding is that this error is unrecoverable so we log the user out and force them to re-authenticate. We have a couple of thousand weekly users and this happens to maybe 2% of them.
One log id as an example:
90020251110035154104236000000000000001223372093331920555
Our top level provider:
<Auth0Provider domain={domain} clientId={clientId}>
<Main />
</Auth0Provider>
Reproduction
Seems to happen randomly, a few times a week for affected users. So far we've only seen it on iOS.
Additional context
A similar issue happens when we use the react version, for both MacOS, iOS, and Windows devices. We allow overlap for expiring refresh tokens (120 seconds). Our refresh token are set to last one year, and we're currently seeing this multiple times a week for users.
react-native-auth0 version
5.1.0
React Native version
0.81.4
Expo version
Not using expo
Platform
iOS
Platform version(s)
Multiple
- Lenguaje dominante
- TypeScript
- Estrellas
- 553
- Forks
- 244
- Merge medio
- 19 h
- PR fusionados (30 d)
- 39
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 auth0/react-native-auth0
-
feature request
Dificultad 4/5 3-5 días Aptitud para principiantes 52/100
auth0/react-native-auth0#1735 ·
Los mantenedores suelen responder en 1 día
-
feature request
Dificultad 5/5 Más de una semana Aptitud para principiantes 45/100
auth0/react-native-auth0#1458 · 8 comentarios · 3 reacciones ·
Los mantenedores suelen responder en 1 día
Todos los issues de auth0/react-native-auth0
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
milind-soni/OpenMausBot#6730 ·
Los mantenedores suelen responder en 1 día
-
`@angular/[email protected]` depends on vulnerable Vite 7.3.7 - GHSA-p4f5-76q4-ffq7 (Critical RCE)Abiertoarea: @angular/build
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
angular/angular-cli#34764 ·
Los mantenedores suelen responder en 1 día
-
status/need-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
google-gemini/gemini-cli#30384 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
P2
Dificultad 1/5 Menos de una hora Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
area:image documentation good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día