Issue: Still showing [native code] even with source maps

[hellsan631]

Really scratching my head here. I am unable to get source maps to correctly work in a provisioned version of sentry, using the latest version of expo & react native.

Releases is correctly set, sentry server version is 9.1.2,
expo: "34.0.4", sentry-expo: "2.0.0",

import * as Sentry from 'sentry-expo';
import Constants from 'expo-constants';

const dsn = 'Something';
const { revisionId: release } = Constants.manifest;

Sentry.init({
  dsn,
  environment: __DEV__ ? 'development' : 'production',
  release,
  enableInExpoDevelopment: true,
  debug: true
});

Sentry.setDist(Constants.nativeBuildVersion); // This doesn't seem to do anything helpful?
Sentry.setRelease(release);

export default Sentry;

Using the post took to upload our source maps, we are still seeing "native code"

Even though this is thrown inside javascript, with build artifacts existing for that release.

[bill-pairaktaridis]

I'm having the same issue. However, it's not happening everywhere. I think it may be connected to the connect() function of Redux. Are you also using it?

[hellsan631]

@bill-pairaktaridis yes. thank you for noticing that.

This is also happening in more isolated areas as well. functional components that do not connect to a store (within their scope), but may well be imported by components that use connect.

We are currently trying to remove redux, but that is a few months away from being complete.

[bill-pairaktaridis]

Yes, maybe one of the sentry-expo devs can help out here. In its current form it offers little in the way of actually debugging an issue.

[b4stien]

I'm under the impression that it's a prefix issue. My code is prefixed with app:/// vs the uploaded sourcemaps that are in ~/. I have an explicit warning telling me Sentry has not found my sourcemaps. Cf screenshots.

[b4stien]

Pinging @HazAT as he wrote the RewriteFrame for app:/// (sorry to disturb if you're not the right person to ask).

[hellsan631]

When i tried to use the base sentry-native repo, it added the app:// prefix, but didnt solve that problem.

I do not have any warnings about sourcemaps.

It also looks like your code is getting some bundle information (onPress, touchableHandlePress), where as mine is just ending at [native code]

[bill-pairaktaridis]

@hellsan631 I'll try adding sentry-native to my project and see how it goes. As it stands right now, I'm not getting any meaningful stack trace within my components/screens

[jacinto123]

I am having this issue as well, anyone got any ideas?

[bill-pairaktaridis]

@cruzach @HazAT could you look into this?

Update: I've forked sentry-expo and updated to "@sentry/react-native": "^1.0.6" but it's still happening. You can see my fork here: https://github.com/bill-pairaktaridis/sentry-expo

The app size is still very large, as well, so I'm not sure the clean up task is running.

Update: Upon further investigation, it looks that at least cliCleanUpTask doesn't run during the Expo build process. Not sure what we can do about that.

[cruzach]

@b4stien I just got the same error shown on the Sentry dashboard ("Source code was not found"), it's due to the release missing. Can you reinstall sentry-expo (made a fix where the release will then be auto-configured on Sentry.init) , and try again?

[b4stien]

@cruzach it works indeed, thank you very much!

[bill-pairaktaridis]

I don't have any errors in my issues. But the code is still showing up minified and with no mapping to the source. I distinctly remember this working for a while (for me) before the upgrade to the unified Sentry JS SDK.

[cruzach]

@bill-pairaktaridis haven't been able to repro this behavior on sentry-expo: "2.0.1", yet. is that the version you're using?

[bill-pairaktaridis]

@cruzach I'm still seeing it. I'll try to set up a clean Expo project and test it on that. Could you also do a rudimentary Redux setup and see if that's the cause? Because right now, this is basically what all my issues look like.

[bill-pairaktaridis]

@hellsan631 did you get it to work?

[bill-pairaktaridis]

@cruzach did you try with a built app (I'm using App Bundles, as that's mandatory now for the Google Play Store)?

[bill-pairaktaridis]

@cruzach I'm seeing that in files that don't contain connect() or react-navigation my errors get reported correctly. So it must be one or the other.

[cruzach]

I don't believe it's react-navigation related, got a project with the most recent sentry-expo working implementing that, already.

I'll try and repro this, if you have time to put together a minimal example using redux that demonstrates this problem, feel free to link a repro

[bill-pairaktaridis]

I'm almost positive it has something to do with connect() or in general something that is in my screens. I've had errors pop up in my newly implemented "models" and they are properly presented. I'll comment back when I have newer issues and we can maybe update the docs to reflect this case, as Redux is promoted by Expo themselves.

[bill-pairaktaridis]

I was able to resolve this! The fault was on my end because I was catching all errors on my AppScreen.js with componentDidCatch. Apparently the way I did it wasn't including breadcrumbs. I removed that and now errors are presented correctly, even though I'd like to be able to centrally handle all errors.

[hellsan631]

@bill-pairaktaridis how did you catch breadcrumbs as well?

[bill-pairaktaridis]

@hellsan631 I didn't. I just removed my componentDidCatch and let Sentry handle it. There's definitely a way to do it but in our current development cycle I was just happy to get it working and being able to debug again.

[alexanderritola]

Sentry docs appear to show how to resolve this.

https://docs.sentry.io/platforms/javascript/react/#error-boundaries

[bill-pairaktaridis]

Unfortunately, this issue seems to have resurfaced. This is the screen I'm looking at again:

I'm pretty sure this error occurs within a fetch statement, if that is any indication

[cruzach]

i think this occurs only for unhandled promise rejections on android

see:
sync func call stacktrace

async func call stacktrace

@HazAT curious if this is an issue specific to sentry-expo or if it could be a sentry or general react native issue?

[bill-pairaktaridis]

@cruzach yes that's what I've surmised as well. I keep getting a couple every day that are all promise rejections that I'm apparently not handling somewhere in the code. Hard to troubleshoot though without any stack trace.

[cruzach]

i think this is a duplicate of #4

[skoch-tf]

check if your source map was published with success:

expo publish

Running postPublish hook: sentry-expo/upload-sourcemaps
Created release 1.3.112-r0-CX15Bte!.

[keith-kurak]

Heads up that I see this same behavior when I call Sentry.captureException() within a MobX State Tree middleware and in a componentDidCatch on my root component. I see a few [native code] blocks on iOS stack traces, depending on the error, but usually get at least some partial sense of where the error is. However, I get almost no useful info out of Android errors. I just put in a support request to Sentry to see if they had any ideas.

[juspeeh]

Also facing similar issues.
expo: 39.0.4
sentry-expo: 3.0.3

Source maps have been uploaded successfully.

[juspeeh]

@cruzach

Any information I can provide to solve this issue? Or any advice I should check on my environment that could cause this issue?

All the errors I'm getting are filled with [native code] and I'm not able to pinpoint any errors from the production environment.

[cruzach]

I believe this was an upstream sentry issue (getsentry/sentry-react-native#1077) and was just recently fixed. Once a new release is published, you'll just need to remove your node modules and lockfile and reinstall sentry-expo@next, since it should automatically pull in the newest version of @sentry/react-native (unless it's a breaking change)

[cruzach]

Newest version of @sentry/react-native was released- 2.2.2