Can't fix warning messages after react native upgrade - reactjs

After upgrading to react native 0.25.1 I get yellow warning messages that don't go away after I make all the changes indicated in the release notes. How can you track down the where the errors are occurring? I've searched and found nothing other than the code called for on this page: https://github.com/facebook/react-native/releases

Related

react native and expo: problem sending log messages symbolicatedStack

Recently I updated react (0.62.2) and expo (37.0.12). Nearly everything works fine. Except upon every App reload and shortly after an error occured, an error screen pops up that displays
console.error: There was a problem sending log messages to your development environment TypeError:
symbolicatedStack.map is not a function. (In 'symbolicatedStack.map(removeProjectRoot)',
'symbolicatedStack.map' is undefined
covering the previously occured error.
since there is no symbolicatedStack written by myself, I suspect its an internal error, but I can't figure out what it is. Upon pressing "Dismiss" everything works fine again. (Till the next reload/error)
Expo / React version are compatible according to their offical websites.
I guess this is dues to version missmatch try running expo upgrade command. It should resolve your issue.

React Invalid Hook Call in Index.js in ReactDOM.render

This problem is killing me, but I keep getting this error when I compile and run (I am using .NET Core 3.0 with react app):
Error: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
You might have mismatching versions of React and the renderer (such as React DOM)
You might be breaking the Rules of Hooks
You might have more than one copy of React in the same app
The error points to my ../src/index.js file:
Here is the error displayed
Here is the code that is flagged with the invalid hook call error
I'm not sure what's going on, i spent the past 3 hours trying to fix it but I just can't get the homepage to show.
I understand the hooks error, but I don't understand why its getting called.
I have the matching versions of React and React DOM, 16.13.1
For my react components, I use classes.
I'm not sure how to check for different copies of react
I'm quite new to React so maybe i misunderstood or messed up somewhere, please help me here, thank you.
EDIT:
Check if redux is installed on the client. This error occurs when it isn't installed on client directory but server directory.
check package.json of client.
Maybe a crazy solution but in my case nothing was actually wrong with my code. I was going nuts trying to find the error. But what actually helped, was upgrading the version of Typescript installed in my project from 4.4 to 4.9. Don't see any evident connection but after the upgrade everything worked like a charm. :)

How can I debug a newly cloned React Native app

I am starting to help someone with a new project. This project is React (React Native as is a mobile app).
The project is working fine on her laptop (in her browser), and when I scan the Expo QR code, the app works fine on my Android device.
However, trying to run it in my browser is throwing all these errors:
The 'Can't resolve' error doesn't make sense, because the correct react native files are there. Is this a cache problem? I have tried deleting the .expo/web/cache folder and starting over.
Also, why are there multiple errors in my console, but only one being shown in the information on the actual web page? Does this mean that the single error being shown is causing all the other errors, or it is the only one which needs fixing, or will it show the next error when I fix the one that is being shown?
Thanks
Seems to have been a known problem re babel. See the links below:
https://github.com/babel/babel-loader/issues/173
how to solve this error You may need an appropriate loader to handle this file type

ReactJS tutorial: does not display the expected unique key warning

I'm new to ReactJS and I'm trying to follow the tutorial here: https://reactjs.org/tutorial/tutorial.html . Everything seems fine except at this step: https://reactjs.org/tutorial/tutorial.html#picking-a-key where it says
For now, we should see a list of the moves that have occurred in the game and a warning that says:
Warning: Each child in an array or iterator should have a unique “key” prop. Check the render method of “Game”.
I've set up my project using create-react-app (following the instructions here: https://reactjs.org/tutorial/tutorial.html#setup-option-2-local-development-environment), did not change any settings, yet for some reason at this step (before a key is added to the li element) when I run "npm start", I don't see the said warning.
I've tried googling for the answer, ironically all the results I've found are people asking how to get rid of this warning, whereas I'm trying to see this warning. Does anyone know what could be happening here?
Thanks in advance!
It is a warning coming from React side and you can see it in your browser's developer tool's console as an error. I know it is weird but I think people turn off the warnings and since keys are necessary for React to handle the list items in a stable way, it is shown as an error.

How to debug failing react 16 components inside a jest snapshot test

Aloha,
I often get an error message when running a jest snapshot test where on sub component breaks. React itself writes the following warning, but keeps the thrown error message:
An error was thrown inside one of your components, but React doesn't know what it was. This is likely due to browser flakiness. React does its best to preserve the "Pause on exceptions" behavior of the DevTools, which requires
some DEV-mode only tricks. It's possible that these don't work in your browser. Try triggering the error in production mode, or switching to a modern browser. If you suspect that this is actually an issue with React, please file an issue.
That message is not really useful and I was wondering if there is a certain environment variable I could set that would cause react to just pass the thrown error on.

Resources