Fernando Rojo

@shuding It seems like the solution you provided which mutates all the open options also doesn't exactly work for me. This is what's happening: ```ts await signOut() await swr.clear() ```...

You could use MMKV if you're willing to install a native library. That uses sync storage persistence with better performance than AsyncStorage. It also works on Web (I added this)....

The [Solito starter](https://github.com/nandorojo/solito/tree/master/example-monorepos/blank) uses Turborepo too – feel free to reference that!

if you're adding navigation, then you should add solito. it'll look the same as Next router/link with the same functionality, in addition to working on iOS/Android

Adding a video for reference: https://www.loom.com/share/0330395f9afd49e5b48c76bf40b2c6fe

This bug still persists. Wondering if there are any plans to support nested git repos. Thanks!

yeah we do. this would happen if you're reading storage in the global scope / in render / not in `useEffect`. this isn't recommended for `localStorage` in general on Web....

this is just a fact of web development. storage doesn’t exist on the server, and react hydration requires that props match on the client and server. so you could use...

Assuming this component renders on the server, you have a few options: ## Import in an effect ```ts import { Platform } from 'react-native' import { useLayoutEffect, useEffect } from...

From `mobx-persist-store`'s [docs](https://github.com/quarrant/mobx-persist-store#storageoptions--reactionoptions): > If you have an app that is Server-side rendering (SSR) you can set the value `undefined` to prevent errors.