There was 1 problem processing this event, Source code was not found.
See original GitHub issueEnvironment
How do you use Sentry? Sentry SaaS (sentry.io) or self-hosted/on-premise (which version?) sentry.io
Which SDK and version? e.g: “@sentry/react-native”: “2.5.2”
Steps to Reproduce
Any issue being reported on the Sentry dashboard comes up with an error There was 1 problem processing this event
. My sentry initialization looks like this:
Sentry.init({
dsn: __CONFIG__.SENTRY_DSN,
environment: __CONFIG__.STAGE,
release: `${DeviceInfo.getBundleId()}@${DeviceInfo.getVersion()}+${DeviceInfo.getBuildNumber()}`,
beforeSend: filterSentryBreadcrumbs,
});
Expected Result
The error should not be shown as source maps and source bundles are present on Sentry.
Actual Result
-
The correct code of line where the error is originating is shown, but the below red error is also shown on the Sentry.
-
Earlier in the previous release, it used to show the error as
[messaging/unknown] SERVICE_NOT_AVAILABLE
, and in the current release it shows it as[messaging/unknown] java.io.IOException: java.util.concurrent.ExecutionException: java.io.IOException: TOO_MANY_REGISTRATIONS
. Any idea why is this change happening, if this can help in finding the root cause.
Issue Analytics
- State:
- Created 2 years ago
- Comments:15 (10 by maintainers)
Top GitHub Comments
Since the original question was answered, I’ll close it, @shubhnik please open a new issue with a detailed description in case you experience new issues, thanks.
@shubhnik you can also remove this line
release: ${DeviceInfo.getBundleId()}@${DeviceInfo.getVersion()}+${DeviceInfo.getBuildNumber()}
, since you are using the scripts provided by the SDK, either removing therelease
or adding thedist
would work.