-
Notifications
You must be signed in to change notification settings - Fork 82
Fix broken debugging caused by missing CallFrame.url #1559
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
a94653e
to
809bfec
Compare
Great to see this one fixed! I'm not familiar with the process, how that fix will be distributed? Is it going to be part of the next Flutter update? If yes, anyway to get it before? Thanks!!! |
Great work on the fast fix! Could anyone let me know when this is available on (flutter/dart)stable, as currently I am unable to properly test my code and downgrading chrome is not an option for me. Thanks EDIT; also if anyone has a timeframe that would also be helpful |
@Statyk7 , @florisdipt You can follow from here to see the current status in Flutter as well as some steps to manually apply the fix if you need to (as of writing, merged to master, but backport for stable is still pending): flutter/flutter#101224 (comment) |
Apparently Chromium deprecated the CallFrame.url field in the debugger protocol:
https://bugs.chromium.org/p/chromium/issues/detail?id=1270316
https://chromium.googlesource.com/v8/v8/+/21f72f82ce854762d6bc1c780d3b108dc1947f5d
Use
remoteDebugger.scripts
instead ofCallFrame.url
to look up the frame url from a chrome script id.Closes: #1557
Related: flutter/flutter#101224