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

captureMessage on Android using attachStacktrace=true does not send the stacktrace #2131

Closed
marandaneto opened this issue Mar 10, 2022 · 2 comments · Fixed by #2577
Closed

Comments

@marandaneto
Copy link
Contributor

marandaneto commented Mar 10, 2022

The JS SDK appends the stack trace to a top-level property instead of the threads interface.
It works on iOS because the event is sent as it is.
It fails on Android because of the round trip serialization, since this property does not exist on Android, it's lost.

  • Android V6 keeps the unknown fields, which would solve the problem (Still alpha tho).
  • The JS SDK could adapt it to use the threads interface (Gonna be done on V7, See the issue).
  • The RN SDK could process the event and move the top-level property within the threads interface.

The 3rd option right now seems faster/easier.

@marandaneto
Copy link
Contributor Author

We've decided to go either with upgrading the Android SDK to v6 or JS SDK to v7, the one that comes first.

@marandaneto
Copy link
Contributor Author

Blocked by getsentry/sentry-javascript#5879

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment