fix(react): race condition between initialize and isAuthorized in RN

[andrascodes]

This PR is part of a stack created with Aviator. feat(expo-example): add export wallet on mobile #168 feat(expo-example): configure and add magic link login #142 fix(expo-example): add EAS local build config and fix HMR bug with secureStoreStamper #141 feat(expo-example): migrate to expo-router #131 feat(react): enable OAuth in React Native #80 feat(expo-example): add Passkey auth and test on Android #124 feat: add expo-example app #76 ➡️ fix(react): race condition between initialize and isAuthorized in RN #75 main

Closes FS-1930

On mobile when passing in a SecureStoreStamper to the SDK I noticed that the session refresh wasn't working properly. The session refresh itself succeeded (so initialize() ran and completed) but the connect() wasn't being called inside wagmi.
Here's the lifecycle of the connector methods in wagmi:

1. In Wagmi: setup() is called in createConfig, it's not awaited, you can see it here - so this just kicks off our session refresh and initialize()

2. In reconnect() (when the user refreshes the app): (here)

   1. getProvider() is called first, awaited, if !provider  then skips - on mobile we have the provider here already so this is truthy and the execution continues to
   2. isAuthorized() : this gets called and awaited, here the eoaAccount that we return is still null when this method is called, because initalize() takes too long likely because of the secureStoreStamper operations. So when this happens the reconnect() doesn't continue. It just skips our connector.

The fix I opted for was awaiting initialize() in getProvider() so even at that point we for sure have the Provider and initialized the session.
An additional fix I opted for was awaiting the hydration of the Zustand store as well. This is best done because on React Native the store can be AsyncStorage with async operations. In order to do this, I passed skipHydration to the store and then in initialize() started and await the store.persist.rehydrate().

This way at the point wagmi calls getProvider() we know we have the store hydrated and the ZDWallet + the Session initialized and set in store. So connect() will definitely be called with the correct state.

On Web: awaiting the hydration should be quick because the store is Sync. Also, IndexedDB is much faster so the initialize() should already be resolved by the time getProvider() (and await initialize()) is called.

[SahilVasava]

LGTM!

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
zerodev-signer-demo	Ready	Preview, Comment	May 13, 2026 11:32am

The base branch was changed.