-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
_normalizeUrl is never called, so sourcemaps aren't connecting (react native) #772
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
Comments
Can you paste the raw JSON of the exception as recovered by Sentry (it's linked in the UI)? (Omitting anything sensitive.) |
|
@sjafri5 – ah, yeah, I see. This is occurring because this is a I've created a second issue to track this: #776. Closing this issue – thanks for bringing this to our attention. For future reference, you should only send errors to |
Hi, so the problem on a macro scale is that the sourcemaps are not matching to the minified code in the stacktraces.
When I upload the artifacts with their full name (i.e.
file:///var/mobile/Containers/Bundle/Application/CF21C92F-695D-47E8-9B63-F5EB40DE0A2F/my-app.app/main.jsbundle
) I get full stack traces. This obviously not scalable since the full url has a specific deviceID.This seemed to be a problem with an updated pathname that the regex didn't cover (#665) but that has been updated and I can confirm that the new regex captures everything except the tail (
/main.jsbundle
).So it seems that the issue is that the
reactNativePlugin._normalizeUrl
(which is where the stripping occurs) isn't being called. It seems that the method_normalizeData
only calls_normalizeUrl
if eitherdata.exception
ordata.culprit
exist. When i run this with debugger, they skip over both of these conditionals. However the JSON that shows up in on server shows a data.culprit with the full URL.Any help would be greatly appreciated.
I am using raven 3.8 and react-native 0.33
The text was updated successfully, but these errors were encountered: