Skip to content
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

Stack frames say "Crashed in non-app" even though the code *is* app code #28849

Closed
Daniel15 opened this issue Sep 26, 2021 · 2 comments
Closed

Comments

@Daniel15
Copy link

Environment

self-hosted (onpremise deployment)

Version

21.9.0

Steps to Reproduce

  1. Add Sentry JavaScript SDK to a project that's bundled using Webpack
  2. Update Webpack config to publish the source maps via the @sentry/webpack-plugin
  3. Intentionally cause a JS error

Expected Result

Stack trace appears in Sentry

Actual Result

Stack trace appears, but it says "crashed in non-app" next to it:

image

If I click the stack frame, it does show the correct code:
image

@getsentry-release
Copy link

Routing to @getsentry/owners-ingest for triage. ⏲️

@Daniel15
Copy link
Author

Duplicate of getsentry/sentry-javascript#3853, fixed by #28859

@github-actions github-actions bot locked and limited conversation to collaborators Oct 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants