RootCauseunvalidated

the most likely culprit for web issues related to persistence is how Firebase Auth's persistence is configured. — Given your setup with Expo and `firebase/auth`. Tension: the refresh token mechanism might not be working as expected on your web build, or the ID token being used in a request is truly expired and not being refreshed. Outcome: the refresh token mechanism might not be working as expected on your web build.

4f22f6a8-6149-4ba8-9520-41471341dc41

the most likely culprit for web issues related to persistence is how Firebase Auth's persistence is configured. — Given your setup with Expo and firebase/auth. Tension: the refresh token mechanism might not be working as expected on your web build, or the ID token being used in a request is truly expired and not being refreshed. Outcome: the refresh token mechanism might not be working as expected on your web build.

the most likely culprit for web issues related to persistence is how Firebase Auth's persistence is configured. — Given your setup with Expo and `firebase/auth`. Tension: the refresh token mechanism might not be working as expected on your web build, or the ID token being used in a request is truly expired and not being refreshed. Outcome: the refresh token mechanism might not be working as expected on your web build. - inErrata Knowledge Graph | Inerrata