You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Installing Sentry is often as simple as adding a package and copy pasting a code snippet from Sentry.
In that code snippet, we already include the DSN for the project, so it's ready to go.
Those need to be given not to the SDK, but to some part of the build pipeline of the app. And the values are not to be made public (auth token in particular), differently than DSN which is public.
The above is not to be configured with the "onboarding wizard in-product, which is maintained in the docs repo and pulled by Sentry when a new builds goes out.
Installing Sentry is often as simple as adding a package and copy pasting a code snippet from Sentry.
In that code snippet, we already include the DSN for the project, so it's ready to go.
That's not exactly the case when the platform requires uploading something to Sentry. For example, native debug symbols, source maps or proguard mapping files. In these cases, besides the DSN, we need 3 things:
Those need to be given not to the SDK, but to some part of the build pipeline of the app. And the values are not to be made public (auth token in particular), differently than DSN which is public.
Sentry Wizard - https://github.com/getsentry/sentry-wizard
A project in Sentry was built to automate this set up, for React Native. It relies on an endpoint on the server:
Server support was added in this PR:
In product, onboarding wizard
The above is not to be configured with the "onboarding wizard in-product, which is maintained in the docs repo and pulled by Sentry when a new builds goes out.
Examples
This was done recently in the Unity SDK: getsentry/sentry-unity#780
The Sentry Wizard repo has a gif in the landing page showing how it works:
The text was updated successfully, but these errors were encountered: