Source code was not found 1.3.0 (iOS & Android)

[valeriashpiner]

OS:

• Windows
• MacOS
• Linux

Platform:

• iOS
• Android

SDK:

• @sentry/react-native
• react-native-sentry

react-native version: 0.61.2
SDK version: 1.3.0

Init Code:

Sentry.init({
  dsn: 'https://...@sentry.io/...'
});

---

I have the following issue:

After update today from 1.2.2 to 1.3.0 with Hermes support, I ran iOS build in release mode and added following line to create crash:

throw new Error ('New Sentry!')

I ran assembleRelease for android and then regular build with the error.

Steps to reproduce:

1. yarn add @sentry/react-native@latest
2. pod install (it updated sentry/react-native to 1.3.0)
3. watchman watch-del-all && rm -f yarn.lock && rm -rf node_modules && yarn && yarn start --reset-cache

Actual result:
I don't see sourcemaps for iOS anymore.

I don't see sourcemaps for android, but 1.3.0 sees Hermes engine.

Expected result:
I would like to be able to see the source of error for ios and android.

Thank you!

[valeriashpiner]

I fixed iOS by uploading source maps manually 😞
It didn't upload for me in the usual way (release mode through XCode).
For android, I still don't see the source maps even after I upload it manually.

[Bardiamist]

Same issue.
Hmm, rollback to 1.2.2 not helped.

[HazAT]

There is a small bug in iOS right now, we are working on a fix.
It sets the wrong release name by default.

[HazAT]

getsentry/sentry-cli#660

[valeriashpiner]

thank you @HazAT! Is android suppose to work? I pushed source maps manually and I see them in artifacts, but I still not see them in error (Source maps wasn’t found).

[HazAT]

@valeriashpiner Can you post a link to an event so I can take a look?
If built in release it should work.
In debug you also should see the code but we have a small bug on the server saying "Source Code not found" but actually the frame is symbolicated correctly.

[valeriashpiner]

@HazAT I think I found android issue! My artifacts and files which Sentry looks for have different names! 😄
I don’t know why they don’t upload through assembleRelease, but I will upload them manually and check.

Thank you for iOS quick fix! ❤️

[HazAT]

Yes, we changed how releases are named, by default sentry-cli should create the new matching releases correctly. Do you invoke sentry-cli manually?

[valeriashpiner]

@HazAT Yes, I made it like this:

react-native bundle \ --dev false \ --platform android \ --entry-file index.js \ --bundle-output index.android.bundle \ --sourcemap-output index.android.bundle.map

and then this:

node_modules/@sentry/cli/bin/sentry-cli --auth-token **[token]** releases --org **[org name]** --project android-app files **[release name]** upload-sourcemaps --dist 3123 --strip-prefix index.js --rewrite index.android.bundle.map index.android.bundle

so far I see bundles in artifacts and Sentry doesn't complain anymore.
as soon as we will receive crash in release mode from users, I will know does it work correctly or not.

[HazAT]

1.3.1 has been released, fixing the iOS issue.

[valeriashpiner]

@HazAT:

I made a build in Release mode. iOS.
Artifacts did not upload.

The error shows in the correct line, but the text is wrong.
I create an error with text Valeria yesterday, today it's `This is error!:
✔️ source maps show me old text
✔️ BUT in exception, it's correct text.

Even when I uploaded source maps manually, I still see old text in error.

[valeriashpiner]

Android with source maps - manual upload (1.3.1):

[christianbach]

@valeriashpiner the same is happening to us when enabling Hermes, using the JSC on android show the correct line number and source code. We create and upload our sourcemaps manually

[valeriashpiner]

@christianbach this release (1.3.0) supposed to fix Hermes issue. I don’t understand why it’s still not working and also iOS source maps are incorrect.