Skip to content

Update react-native-sensitive-info to v6 - #3927

Merged
jtklein merged 10 commits into
mainfrom
mob-1638-update-react-native-sensitive-info-to-v6
Aug 17, 2026
Merged

Update react-native-sensitive-info to v6#3927
jtklein merged 10 commits into
mainfrom
mob-1638-update-react-native-sensitive-info-to-v6

Conversation

@jtklein

@jtklein jtklein commented Aug 11, 2026

Copy link
Copy Markdown
Member

Closes MOB-1638 (also closes MOB-1160)

Summary

  • Upgrade react-native-sensitive-info 5.6 → 6.1.5 (Nitro) and adapt auth storage wrappers/tests to the v6 API.
  • On startup, if Realm still has a signed-in user but secure tokens are missing, send them through the existing “Please log in again” flow.

Test plan

  • Fresh login / sign-out still stores and clears tokens
  • Upgrade path: signed-in Realm + empty secure store → re-login screen for the same user

jtklein added 10 commits August 11, 2026 14:42
If they contradict we probably lost the access token. For example, in this upgrade PR we loose the previous auth tokens state and are unable to authenticate to the API as the current user. So, in order to not loose all saved observations, and other realm state, we route to the login screen to login again and obtain new auth credentials.
@jtklein
jtklein marked this pull request as ready for review August 11, 2026 16:27
const { i18n } = useTranslation( );

useEffect( ( ) => {
const id0 = deferTask( "checkLoggedInStatuses", async () => {

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could this miss the re-login flow if navigationRef isn't ready when this deferred task runs? Since this is a one-time check, it looks like wouldn't retry once navigation becomes ready
maybe I'm wrong ...

@sepeterson sepeterson left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code looks good.

I did find that the upgrade path on android seems to require sign-in again. Probably good to get this out now. iOS went fine

@jtklein
jtklein merged commit a474c02 into main Aug 17, 2026
17 checks passed
@jtklein
jtklein deleted the mob-1638-update-react-native-sensitive-info-to-v6 branch August 17, 2026 08:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants