async-storage | React Native hook for Async Storage | Storage library

I have a login page. There, the user enters data and submits to the API. The API gives an answer that there is such a user and gives him an id from the database. I write this id in storage. Next, the user is taken to the home page. There is a component that is responsible for getting the username (and indeed all other data) the essence of the component: 1 The parameter receives an id and forms it into a json request. 2 The parameter sends this request to the API and receives the user's data in the response (if the id matches) 3) return which draws the interface and gives the user data from the API response

Problem: When changing an account (or re-logging in), it gives a json request error (in fact, the API does not accept an empty request, so it rejects it) The point of getting an ID is 100%. When the application is updated again, the id turns out to be generated in json and after that I already get data about the user.

How to fix it? In fact, it must first receive the id, and only then the id is sent and the data is received, however, at the first entry into the application, he does not want to receive the ID immediately, but only after a reboot (ctlr + s in VS code)

//LOGIN.js

Shaking the android device and hit Debug, and it crashes every time right away. From the Android Studio logcat, it shows No source URL loaded, have you initialised the instance?:

So I wrote a to-do list app, following a youtube tutorial, but it does not work as intended, it does not save the changes made so when you open the app again it starts as nothing happened. I installed async storage with the command npm i @react-native-async-storage/async-storage and linked it with the command react-native link. Maybe I'm linking it wrong or idk I'm completely new to this. Here's the App.js:

It was working fine before I have done nothing, no packages update, no gradle update no nothing just created new build and this error occurs. but for some team members the error occur after gradle sync.

The issue is that build is generating successfully without any error but when opens the app it suddenly gets crash (in both debug and release mode)

Error

I have a react-native project. After the bitnary (jcenter) shutted down I started to replace it. Currently I'm using mavenCentral(). Also I'm using the react-native-intercom (wrapper for intercom). When I'm trying to build gradlew assembleRelease. Its throws me an error.

I'm creating an Auto-Logout functionality (which needs to be logged out every day at 9 am) in my react-native app, so for that I came up with the logic:

So what I'm doing is, lets say I have my parent stack component, in that inside the useEffect, suppose the app is just opened, I will check if I have lastRunTime saved in async-storage, if true, then I will create a new Date object pointing today's current date, then if 9:00 am comes in between these 2 times, I will logout and set lastRunTime as Date.now().toString() in async-storage.

I have got the following package.json file. Main purpose is to use Expo 44 with native-base (version ^3.0.0). I could not figure out why such an obvious combination does not work. (Could not find online for native-base, which Expo versions are recommended either.)

package.json:

I am developing an app using react native, every time I refresh the app on the emulator in onAuthStateChanged and currentUser from firebase I get null.

I have read about waiting onAuthStateChanged to get a status update but I never do, so I guess I misconfigured something.

I am using expo 44, react 17, firebase 9.6.5 but in compat mode (planning in fully migrate later)

My first attempt of solution was trying to add persistence: firebase.auth().setPersistence(firebase.auth.Auth.Persistence.LOCAL);

I'm only seeing mention of changes in babelrc etc. online for this message. I've tried to remove the dependency that gives me this error and it appears that then next dependency evaluated returns the same message.

The error is coming from any/all of my node_modules folder and the code is correct. I'm guessing something has changed w/ versions of something in my dev dependencies but not sure how to track it down...

I'm using RN 61.5 old I know but this is a production env and can't update atm. Any help on where to look to find the issue please?