-
-
Notifications
You must be signed in to change notification settings - Fork 342
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
feat: Unified API + Transport + iOS #591
Conversation
Body Fixes #123
* feat: Use @sentry/browser * feat: Moved all code into src * fix: First working version * feat: Unified API + Transport + iOS (#591) * feat: Native transport * feat: Move ios/android code * feat: Handle promises + nativeCarsh * feat: Use device context, Trim public API * feat: Make android work * fix: Remove unused transport * feat: Add native android send * fix: Use older android code * fix: Small Android changes * feat: Fetch release from native * meta: Changelog + versions * meta: Update Sentry wizard * meta: Changelog * Update CHANGELOG.md Co-Authored-By: Kamil Ogórek <[email protected]> * feat: Codereview changes
|
||
RCT_EXPORT_METHOD(setTags:(NSDictionary *_Nonnull)tags) | ||
{ | ||
SentryClient.sharedClient.tags = [SentryJavaScriptBridgeHelper sanitizeDictionary:tags]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry I realize this is months old now @HazAT but it appears this was removed in the new API and therefor impacts react-native ability to report context on native crashes, see #694 - I can push up a PR if this was accidental.
However, a bit confused on how that would work in this new API, seeing as setTags
is just exported directly from @sentry/core
- is it possibly to create some sort of proxy so native context is added as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will fix this, instead of setting all properties individually we will just persist the Scope.
Keep an eye on the issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @HazAT
No description provided.