Roboz Béla

My experience with the topic above: https://github.com/expo/expo/issues/24273

> I have investigated this bug recently : > > * The bug comes from the serializer, which injects [environment variables into the bundle](https://github.com/expo/expo/blob/359f1da6e77431f18adbaccc10b5110d13266e2d/packages/%40expo/metro-config/src/serializer/environmentVariableSerializerPlugin.ts#L107) : it injects lines of code...

The workaround was: using node 16.18.1 instead of the latest

By adjusting the settings, I managed to bring it to life, but I find it very cumbersome to use, so I decided to leave it as it is.

Nothing works for me at all.

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...

> 🎉 This issue has been resolved in version 1.2.1 🎉 > > The release is available on [GitHub release](https://github.com/expo/vscode-expo/releases/tag/untagged-5434ff418e290dad76f0) > > Your **[semantic-release](https://github.com/semantic-release/semantic-release)** bot 📦🚀 

My first experience with the new version: https://github.com/expo/vscode-expo/assets/8656998/021ebb9a-56fd-4a9a-b164-2cdb5127a53a Thank 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...