I have an app that works fine in Expo Go. I’m able to shake the device and Debug Remote JS.
Soon it will need to be transitioned to an EAS build so I decided to try it as is.
To my surprise when turning on Debug Remote JS the metro server immediately crashes.
RuntimeError: abort(FetchError: invalid json response body at http://[::ffff:c0a8:15d]:19000/json/list reason: Unexpected token < in JSON at position 0). Build with -s ASSERTIONS=1 for more info.
at process.abort (/node_modules/metro-hermes-compiler/src/emhermesc.js:402:15)
It seems like a Hermes issue but I’m not sure how to troubleshoot.
Thanks for any pointers in the right direction to troubleshoot!
it’s useful to share a bit more info about your project, and whether you can reproduce this on a new project. eg: npx expo-env-info dumps a bunch of details
Thanks Brent,
I just built this app from a fresh expo-router build. Waiting 15-20 minutes for each build to run when debugging a build specific issue really crushes my moral. For that reason, I always try asking in case someone already knows the issue.
I will go back and start from scratch after trying a couple other things with the existing bundle.
If you have a directory in your project called android containing a file called build.gradle then expo-env-info says it’s bare.
If you have a directory in your project called ios containing a subdirectory called something.xcodeproj then expo-env-info says it’s bare.
Otherwise it says managed.