Repository navigation
fix(mobile): keep account loaded after a failed identity refetch - #5981
Merged
Merged
Conversation
Foreground refresh of user.getMe can fail after a long background while the cached user is still valid. Bootstrap treated that as "could not load account".
iscekic
enabled auto-merge (squash)
September 9, 2026 08:39
eshurakov
approved these changes
Sep 9, 2026
This was referenced Sep 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Review and merge. After a long background, a failed
user.getMerefresh no longer replaces the app with Could not load account.Cause
user.getMe.isErroreven when the cached user was present.Change
useCurrentUserIdreports an identity error only whendatais missing.Test
apps/mobile:vitest run src/lib/hooks/use-current-user-id.test.ts— 5 passed.