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.
Related
[these error are showing when i was try to run my first react project. I don't know how to fix please help.][1]
[1]: https://i.stack.imgur.com/Acb0i.pngstrong text
For me, the problem was another instance was running. Search for other react instance running and kill it. It should resume properly after.
Or this is happening because nothing is listening on your adresse:port
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
I am developing a mobile app with React native and trying to use firebase as a database. Yesterday I tried to upgrade my React native version from 0.37 to 0.40 but some files conflicted and my app didnt start. So I reverted to version 0.37. ( I copy pasted conflicted files with my earliest copies to solve this)
Now, when I copy paste firebase code snippet to my App.js file to setup firebase, I get an error "Cannot read property 'getItem' of undefined"
If I remove firebase snippet everything works fine. Otherwise after 1-2 seconds red screen pops up with the error on attachments.
I am suspecting, I broke something on the way to reverting react native 0.37. I tried to uninstall and reinstall firebase with no avail. Now I am beating my head and any help would be greatly appreaciated.
I found a solution to my problem. It seems that problem is not with firebase but its because of chrome debugger. Having the 'device toggle toolbar' (CMD SHIFT M) enabled in chrome seems to be causing the problem. De-selecting 'device toggle toolbar' and reloading the emulator gets rid of the error.
Check the image link for sample please.
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
I cloned the following Polymer todo-list app from https://github.com/PolymerLabs/todo-list and after setting it up as per the instructions, i got it running on local with gulp serve. I could signin and add/delete/update todos as expected. However, a colleague of mine who did the same thing is getting the following error
My colleague is working from the Philippines if that matters at all. Could someone please advise how I can get it working on his local machine? We're both using Chrome btw and he does not run into any issues using a version that was deployed to firebase, just encountering the error on localhost. Thanks.
The issue was caused by the firebase element as explained here. Updating the firebase element solved the problem.