Files

T

History

Icaro Motta b89dce3c2a chore(analytics): Integrate Sentry (#21682 )

Integrate Sentry and implement a feature flagged feature (disabled by default)
to force crash the app using the function mobile/status.go#IntendedPanic()
provided by status-go. Because the feature is feature flagged and disabled, it
is not available in release builds.

Fixes: https://github.com/status-im/status-mobile/issues/21656

Documentation about Sentry in status-go:
https://github.com/status-im/status-go/blob/3466ac2661bb19cd0eaa27761551de3b4d31b393/internal/sentry/README.md#L60

Areas that may be impacted: Whenever a panic happens in status-go and usage data
collection is enabled we will send error data to Sentry. In theory, nothing
should change for the user, therefore nothing should be visibly different in the
app's behavior.

Steps to test:

Before following the steps below, the CI must be configured with the appropriate
SENTRY_DSN_STATUS_GO value. You can also use a free tier cloud instance to do
your own testing in case you want to play around with Sentry.

1. Login with any profile.
2. Enable usage data collection (for now, Sentry and analytics are tied to the
   same setting in status-go).
3. Go to Settings > Feature flags and enable app-monitoring > intentional-crash
4. Go to Settings > Advanced > and press on Force crash immediately

Usually you should see the error in the Sentry dashboard in a matter of seconds.

2025-02-24 19:28:38 -03:00

tests

chore(analytics): Allow MixPanel to be configured per env (#21975 )

2025-02-24 00:06:59 -03:00

tools

chore(analytics): Allow MixPanel to be configured per env (#21975 )

2025-02-24 00:06:59 -03:00

Jenkinsfile

remove old jenkisnfiles

2018-09-04 07:39:40 -04:00

Jenkinsfile.android

chore(analytics): Integrate Sentry (#21682 )