reactotron | desktop app for inspecting your React JS | Frontend Framework library

Disable the rule, at least in this line. It is what it is.

Seriously, this rule is harmful. You do not need to have each and every existing eslint rule active and rules that force annotation with certain types are especially harmful, causing you to remove available type information.

If something is wrong, you will still get a type error, just at usage of the function, not at definition.

There is one place where you need to annotate types and that is in function input positions - because there they cannot be inferred. Everything else is optional. Sometimes it helps readability, sometimes it actively hinders it. Use your mind at that point, don't stick to a fixed rule.

Especially with Redux Toolkit, you get a lot of very specific types and manually annotating those will require you to either duplicate your code in types, or to annotate it in a way that you lose valuable information.

Based on your package.json dependencies you dont have the @react-native-async-storage dependency, you have @react-native-community/async-storage, which is the old organisation namespace.

Try doing

You should return the response.json(); on the first .then function for it to be available on the next .then.

Do this:

Looking at the code, it's first saving and then it's updating the array, so you will always be one step behind on your storage:

You'll need to do a few things

1. If you don't already have a .babelrc, create one and add the following

Thank you all for the support, after multiple efforts of solving this, I found the solution was related to my network making IPV6 requests instead of IPV4, I don't filly understand this but this is how I solved:

System Preferences > Network > Advanced > TCP/IP > Configure IPv6: Link-local only

Source

After I had written out this question, and started picking SO tags, and had to decide upon using mobx-react vs mobx-react-lite or both, I remembered the issues I ran into during the last upgrade I went through, which switched between those two, and the use of inject and observer.

So I realized that maybe my navigator needed to be observable...

Importing mobx-react-lite and wrapping RootStack in the following fixed everything for me.

The error is perfectly legitimate, pointing out that Detox works as expected.

When it comes to test orchestration and execution, Detox is in fact a mere wrapper around an actual test runner -- Jest in your case (the better choice IMO :). That fact is mentioned in the setup guide and explained more elaborately in the more specific guide for setting up Jest:

Instead of navigate, you can use replace to replace a screen so the previous screen will be removed. It'll be similar to how navigate works in switch navigator.

https://reactnavigation.org/docs/en/stack-actions.html#replace