Convex Auth signaling unauthenticated in RN after inactive
I haven't been able to capture much on this, but I've seen this consistently since migrating to Convex Auth:
- After opening the iOS app when it's been in the background, we're redirecting to sign in
- The logic currently in place will only do this if both
- I've added logic to listen for further changes to these values, and also added a user query that waits for an authenticated user to come back, none of this is working
- Closing the app completely and reopening causes the currently authenticated user to be recognized
I'm trying to get more insight to share, but wanted to bring this here in case anything jumps out at anyone. It's becoming a bit of a pain that the app effectively redirects to sign on most occasions, even though the user is authenticated. I'm not building for web, and am only assuming this is RN specific. Maybe something to do with secure storage?
- After opening the iOS app when it's been in the background, we're redirecting to sign in
- The logic currently in place will only do this if both
isAuthenticated and isLoading from useConvexAuth() are false- I've added logic to listen for further changes to these values, and also added a user query that waits for an authenticated user to come back, none of this is working
- Closing the app completely and reopening causes the currently authenticated user to be recognized
I'm trying to get more insight to share, but wanted to bring this here in case anything jumps out at anyone. It's becoming a bit of a pain that the app effectively redirects to sign on most occasions, even though the user is authenticated. I'm not building for web, and am only assuming this is RN specific. Maybe something to do with secure storage?
