You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When integrating Sentry into a React Native project alongside javascript-obfuscator, there appears to be a conflict in the Metro configuration settings. This leads to inaccurate source map line numbers when attempting to trace errors through stack traces.
Environment
React Native Version: 0.70.10
Sentry Version: 5.15.2
obfuscator-io-metro-plugin: 2.1.1
Hermes Enabled: Yes
Steps to Reproduce:
Integrate Sentry according to their documentation by adding settings to metro.config.js.
Integrate javascript-obfuscator using obfuscator-io-metro-plugin.
Run the project build.
Generate an error and observe the source map line numbers in Sentry.
Expected Behavior:
Accurate line number mapping in source maps when using Sentry and javascript-obfuscator together.
Actual Behavior:
The line numbers in the source maps do not correspond accurately, hindering debugging efforts.
When integrating Sentry into a React Native project alongside javascript-obfuscator, there appears to be a conflict in the Metro configuration settings. This leads to inaccurate source map line numbers when attempting to trace errors through stack traces.
Environment
Steps to Reproduce:
Integrate Sentry according to their documentation by adding settings to metro.config.js.
Integrate javascript-obfuscator using obfuscator-io-metro-plugin.
Run the project build.
Generate an error and observe the source map line numbers in Sentry.
Expected Behavior:
Accurate line number mapping in source maps when using Sentry and javascript-obfuscator together.
Actual Behavior:
The line numbers in the source maps do not correspond accurately, hindering debugging efforts.
Metro Configuration (metro.config.js):
The text was updated successfully, but these errors were encountered: