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

feat: Unified API + Transport + iOS #591

Merged
merged 12 commits into from Jul 2, 2019
Merged

feat: Unified API + Transport + iOS #591

merged 12 commits into from Jul 2, 2019

Conversation

HazAT
Copy link
Member

@HazAT HazAT commented May 27, 2019

No description provided.

@HazAT HazAT self-assigned this May 27, 2019
@HazAT HazAT marked this pull request as ready for review July 2, 2019 11:54
@HazAT HazAT merged commit 138725f into feat/1.0 Jul 2, 2019
@HazAT HazAT deleted the feat/unified-api branch July 2, 2019 11:54
HazAT added a commit that referenced this pull request Jul 3, 2019
* 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 <kamil.ogorek@gmail.com>

* feat: Codereview changes

RCT_EXPORT_METHOD(setTags:(NSDictionary *_Nonnull)tags)
{
SentryClient.sharedClient.tags = [SentryJavaScriptBridgeHelper sanitizeDictionary:tags];

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?

Copy link
Member Author

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.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @HazAT

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants