Use secret Sentry DSN value (#4210)

* Use secret Sentry DSN value.

We realised our DSN entry has been shipped along with the code and it was being used in several forks as is, resulting in wrong bug reports coming into our Sentry dashboard and making it very hard to debug actual issues in the app.
This commit is contained in:
Jorge Martin Espinosa 2025-01-29 13:47:06 +01:00 committed by GitHub
parent 55399798b6
commit 9b5b76203f
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
11 changed files with 52 additions and 14 deletions

View file

@ -2,10 +2,16 @@
<!--- TOC -->
* [TODO](#todo)
* [Sentry](#sentry)
<!--- END -->
## TODO
## Sentry
There is no analytics in the project yet.
To make Sentry analytics and bug reporting work, you need to provide a Sentry DSN in the `local.properties` file, or set the `ELEMENT_ANDROID_SENTRY_DSN` environment variable.
The format used to add the DSN to your `local.properties` file is the following:
```properties
services.analyticsproviders.sentry.dsn=https://your-sentry-dsn/project-id
```