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

Release Health without native layer support #1427

Open
bruno-garcia opened this issue Mar 25, 2021 · 4 comments
Open

Release Health without native layer support #1427

bruno-garcia opened this issue Mar 25, 2021 · 4 comments

Comments

@bruno-garcia
Copy link
Member

Currently RN release health is powered by the native layers. That is: sentry-android for Android and sentry-cocoa for iOS and macOS. For Windows, we have no native layer, so only features available in the JS-layer are available.

One big feature that users lose is release health. This task is to add RH support directly at the JS layer to unblock React Native JavaScript-only use cases (at this time only Windows support).

@jennmueng
Copy link
Member

This would also add release health/session tracking for expo

@marandaneto
Copy link
Contributor

Maybe we could align the public API with this issue #927 which is also about tracking release health manually.

@marandaneto
Copy link
Contributor

One big feature that users lose is release health. This task is to add RH support directly at the JS layer to unblock React Native JavaScript-only use cases (at this time only Windows support).

One other option would be to be using sentry-native for Windows support and its release health feature, similar to Android and iOS.

@marandaneto
Copy link
Contributor

marandaneto commented Mar 4, 2022

@bruno-garcia I believe sentry-javascript already offers the release health feature, right, should this feature track sessions automatically (by the browser) or just offer a startSession/endSession API?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

6 participants