expo VS async-storage

I am using expo setup with tabs template.

Before we begin working on our project, we must set it up and install all the necessary dependencies. We will be using Expo for this project. Expo is a React Native management tool that handles a lot of heavy stuff for us, such as efficiently compiling code and assets, as well as provides us with a productive development environment. Also we will be using Typescript for this project, but don't worry, the process is practically identical to Javascript, so if you don't know Typescript that's fine. This article assumes some basic understanding of React and React Native , such as components, hooks and state. You must also have Node.js installed on your computer.

Expo saves us from the complex configurations required to create a native application with the React Native CLI, making it the easiest and fastest way to build and publish React Native apps.

- Try to unblock usage of Google Maps in my ReactNative Android, iOS and Web App. Context: "https://github.com/expo/expo/issues/23347#issuecomment-16264...

- Provide financial report to investors (this will likely take at least two blocks)

- Fix initial Zoom setting for Google Maps in my app for web. Context: https://github.com/teovillanueva/react-native-web-maps/issue...

- Check on analytics + user enqueries and write (back) to at least 3 of our most active users in the last couple of days

Timeblock exhausted. Posting this and jumping on first task from above.

But some bugs don't get fixed for years. E.g. there was an issue with expo-secure-store not working well on android after app reinstallatiins. It apparently got fixed now 5 years after it was reported: expo-secure-store bug

\[@RNC/AsyncStorage\]: NativeModule: AsyncStorage is null. To fix this issue try these steps: • Rebuild and restart the app. • Run the packager with \`--reset-cache\` flag. • If you are using CocoaPods on iOS, run \`pod install\` in the \`ios\` directory and then rebuild and re-run the app. • If this happens while testing with Jest, check out docs how to integrate AsyncStorage with it: https://react-native-async-storage.github.io/async-storage/docs/advanced/jest If none of these fix the issue, please open an issue on the Github repository: https://github.com/react-native-async-storage/async-storage/issues 5 | import { ReactQueryDevtools } from '@tanstack/react-query-devtools'; 6 | import { Platform } from 'react-native'; > 7 | import AsyncStorage from '@react-native-async-storage/async-storage';

Storage: redux-persist, @react-native-async-storage/async-storage

You want this: react-native-async-storage

What do you mean by local storage? The browser based localStorage API does not exist by default in react-native. There is an analogue though... The most basic package that most people use, AsyncStorage is just a string based key-value store: https://github.com/react-native-async-storage/async-storage . It's very useful for anything simple. It also has a merge function which lets you automatically update stringified JSON objects without unpacking them and doing the modifications yourself.

Android - SQLite

Since the original React Native AsyncStorage was deprecated, you may be using the community solution: react-native-async-storage. I would personally recommend it!

I think that you using a deprecated package to store your state. Verify if you are using https://github.com/react-native-async-storage/async-storage.

State management, orchestrating HTTP requests, synchronizing client and server state: all these things will apply to React Native. The differences will only arise when the device layer comes into play (for example, if you have to store data on the client, window.localStorage doesn’t exist, but AsyncStorage does.)