async-storage VS react-navigation

AsyncStorage for data persistence

\[@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.

React Navigation Docs

✅ React Navigation –For smooth screen navigation. Guide

Deciding on a navigation library is one of the most discussed topics in the React Native community. One of the top advantages of React Navigation is theme support. This offloads the implementation of making themes from developers.

No Built-in System: Unlike Android's core Intent and Activity systems, React Native doesn't have a built-in navigation framework. Instead you need to chose a 3P library, React Navigation being the most widely adopted solution.

2. React Navigation – Seamless Navigation Made Easy 🗺️

Navigation: While in React you might typically using React Router for web navigation, React Native has its own React Navigation library. This is because React (Web) typically uses URL-based navigation, where different components are rendered based on the current URL path. Whereas React Native uses stack-based navigation, mimicking the native mobile app experience. Screens are ‘stacked’ on top of each other, with transitions pushing new screens onto the stack or ‘popping’ them off.

Unlike React apps that rely on React Router for navigation, React Native uses libraries like React Navigation. You'll need to understand how stack navigation, tab navigation, and drawer navigation work in a mobile context.

React Native: Navigation is more complex due to native mobile paradigms. It uses libraries like React Navigation or Native Navigation, which enable stack-based navigation patterns similar to those found in native apps.

This template was built using a variety of powerful frameworks and tools, including: .NET, Ngrok, JWT (JSON Web Tokens), Entity Framework, AutoMapper, FluentValidation, Flurl, Humanizer, libphonenumber-csharp, MailKit, OAuth, Serilog, Twilio, Swagger, React.js, React Native, React Navigation, Axios, Expo Dev, Lodash, NativeWind, React Hook Form, Zustand, Visual Studio Code, Visual Studio, Android Studio, Git, GitHub Copilot, Node.js, React Native Paper, NextUI