Sentry not showing source

[theahmadzai]

Hi, I'm using sentry for react native I have integrated it with gradle it uploads the sourcemaps fine, but I'm getting this error on sentry UI.

We have couple of white-label apps that have same source code but different version and id, I want to know what am I missing
I see that it uploads source maps correctly for each app and version to the senty I can see that

This is how clicking on uploaded source maps look

I also see some stuff uploaded to Debug Files section but ProGuard is empty

Thanks alot

[krystofwoldrich]

Hi,
I'm sorry for the late response,
At first glance, it looks like everything is uploaded correctly.

Does this warning happens with all the app or some of them are symbolicated correctly and only some of them are not?

Could you check specifically the mentioned release in the error, [email protected]+34?
What does its release bundle look like?

[krystofwoldrich]

As long as the app can be identified by a release name and dist it's not a problem. Do you have a different dist for Andoird, iOS builds of the same release or do you have a release for Android and a release for iOS?

[theahmadzai]

The dist number should be the same for both Android and iOS but currently we only increment dist for Android also at the moment we are only uploading source maps when bundling Android.

Same source code example:-

Android

Package: com.tryperdiem.wh.perdiemcoffee
Version: 2.5.5
Dist: 237 (incremented each release)

iOS

Package: com.tryperdiem.wh.perdiemcoffee
Version: 2.5.5
Dist: 2 (same for all releases)

This is our sentry initialize

Sentry.init({
  dsn: SENTRY_DSN,
  tracesSampleRate: 1.0,
  environment: ENV,
  attachScreenshot: true,
  attachStacktrace: true,
});

[krystofwoldrich]

Okay, thank you so the dist is not the problem.

And the stack trace is not symbolicated bot on Android and iOS for you?

[theahmadzai]

I don't know what does it mean but it looks like this

[krystofwoldrich]

Not symbolicated means you are not seeing the original unmodified functions and file names.
Are you still having this issue or did you manage to resolve this?