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

Streamline exception handling #115

Merged
merged 7 commits into from
Jun 23, 2017
Merged

Conversation

HazAT
Copy link
Member

@HazAT HazAT commented Jun 21, 2017

This streamlines the exception handling and always uses raven-js to capture the exception, we just use the native client as a transport layer.

@HazAT HazAT self-assigned this Jun 21, 2017
@HazAT HazAT changed the title [WIP] Steamline exception handling [WIP] Streamline exception handling Jun 22, 2017
@vafada
Copy link

vafada commented Jun 22, 2017

@HazAT

If you just use native code as a transport layer then what's the advantage of using native code vs using raven-js to send message/data to sentry server?

also does this change capture native errors/stacktrace (not JS errors, Java or Objective-C error) and report to sentry server?

@HazAT
Copy link
Member Author

HazAT commented Jun 23, 2017

Hey, we recommend using the native code as a transport layer because you get a lot more useful information out of your crashes. Mostly information about the device.
I've updated the readme and added more screenshots why it's better :)

@HazAT HazAT changed the title [WIP] Streamline exception handling Streamline exception handling Jun 23, 2017
@HazAT HazAT requested a review from mitsuhiko June 23, 2017 07:53
@HazAT HazAT merged commit 51a4692 into master Jun 23, 2017
@HazAT HazAT deleted the feature/streamline-exception-handling branch June 23, 2017 07:55
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.

3 participants