Expo Tools debuger: could not read source map for... #226
Comments
|
Hi @robozb! Thanks for the report and log data, I think there are a couple things here:
For the first issue, is it possible to send me the initial part of the source map (I don't need all of it, I just want to know the paths defined in that sourcemap). To get that sourcemap, start Expo and open it on your phone:
If neither doesn't work, lmk your Expo SDK version and your entry point. |
|
Dear @byCedric Thank you so much for your quick answer! I'l like to focus to the debugging problem. Without the proper source mapping the break points are incomprehensible. I'm at totaly another place in the source code where the real stop is. Can I resolve the problem, do you know any reliable solution or technique, or tools for this task?
I made a public repo for this short test project: http://127.0.0.1:8081/index.map?platform=android&dev=true&hot=false&lazy=false Maybe there is a serious problem I don't know how can I turn on the source maps in React Native Expo project?! Thank you so much! Bela |
|
Thanks for the info again @robozb! Ah, I think you can use this link for your project: I have a fix ready, but I can't reproduce this issue on my machine. So maybe you can help validate the fix for me. If you add a {
"configurations": [
{
"type": "expo",
"request": "attach",
"name": "Debug Expo app",
// Instead of using `${workspaceFolder}`, use the actual path with the Uppercased drive letter
"projectRoot": "C:\\Users\\Beci\\Desktop\\ReactXepo\\AwesomeProject",
"bundlerPort": "8081",
"bundlerHost": "127.0.0.1"
}
]
}
|
|
🎉 This issue has been resolved in version 1.2.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
I just published a pre-release with a potential fix included. You can switch to this version through VS Code, more info here. Please try version |
|
|
Thanks, seems like a semantic release issue. It's this release https://github.com/expo/vscode-expo/releases/tag/1.2.1 |
|
My first experience with the new version: 2023-09-04-16-58-40.mp4Thank you! |
|
Same error with absolute path as well: |
|
Dear @byCedric Wow, it seems It is working but the lack of source maps still exists :(
The real and source debugger points are different :( Thank you so much for your kind help! Bela |
Wow, you were right, here is the output of this: How can I force your debuger tool (VSCode - Expo Tools) to use this maps(?) to handle the debugger point properly? Thanks, thanks! |
|
I tried a completely new Android Studio, VScode, React Native Expo installation on another machine, the bug is same, the breakpoints is shifted, the debugging is useless :( 2023-09-05-02-41-21.mp4 |
|
It seems the problem is related with expo sdk 49. I tried all the things with Expo SDK 48, and the debugger works fine with proper breakpoints! 2023-09-05-04-17-59.mp4Both demo projects: |
|
Interesting but it seems the extension doesn't manage well the source mapping in some cases(SDK48), while the Chrome DevTools works well. |
|
For anyone on Windows trying to work around this. It appears that it is related to project files not being located on the same drive as the VS Code installation. For me it worked to move the project files to the same drive as the VS Code installation. |
Thanks for the info! I have a similar setup, Windows & vscode is installed on |
don't know why this is not mentioned anywhere this is kind of stupid tbh |
The debugger on Expo SDK 49 was broken by a merge in the babel-preset-expo package which inlined environment variables in the sourcemap after the sourcemap had been generated. expo/expo#25239 was merged in 9.9.0 which fixed the debugger. A workaround for Expo 49 is to disable |
Description of the bug
The one-click debuging function doesn't work
To Reproduce
What steps did you perform which led to this issue?
Expected behavior
The Debuger stops at my breaking points
Actual behavior
Nothing happen, doesn't stop at breakpoints, Debug console:
Additional context
Can you further explain the issue? E.g., information about version/environment or screenshots.
Thank you so much: Bela
The text was updated successfully, but these errors were encountered: