Open stefan-schweiger opened 1 year ago
same here
Hi all! Can either one of you create a repository for me to test a few things? I suspect it might be related to the dev server responding to <bundlerUrl>/json/list
as being a page or screen of your app, instead of returning the correct CDP response.
CDP response from the protocol specification:
@byCedric https://github.com/stefan-schweiger/expo-debugger-bug maybe there is a bit more to trim, but I can simulate the behavior with this (in expo go as well as in my own devclient)
@byCedric if you find the time can you let me know if the repro behaves the same for you?
@byCedric any update on this?
Hi, I'm having the same issue as well. Would love updates.
I got the same issue too.
I got this issue too.
I'm having the same issues as well
Just worked it out, at least for me.
npx expo start
a
Debug Expo app
Voilà
Description of the bug
When I start the debugger via "Expo: Debug Expo app on a device or simulator, using Hermes" I get an popup which tells me
Expo debug: waiting for bundler on 127.0.0.1
but nothing happens. From monitoring the network traffic I see that requests are made tohttp://127.0.0.1/json/list
which just error out with 404.The weird thing is that the debugger was working for me a few weeks ago and also just accessing
http://127.0.0.1
returns a valid response:Expected behavior
Debugger should start correctly
Actual behavior
Additional context
Extension version 1.0.7 (but I have also tried the current pre-release)