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

Stop crashlytics poisoning by developer builds #157

Open
davecraig opened this issue Sep 23, 2024 · 0 comments
Open

Stop crashlytics poisoning by developer builds #157

davecraig opened this issue Sep 23, 2024 · 0 comments
Labels
platform Build and release infrastructure
Milestone

Comments

@davecraig
Copy link
Contributor

The aim here is to stop developers who have a valid google-services.json file from automatically reporting development crashes against release versions. It's not clear the best way to do this. The current approach is that there is a dummy google-services.json file which doesn't point to our app. However, this results in lots of errors in the logs which make them harder to read. Ideally we'd have a valid JSON file that either pointed somewhere other than our app, or had a different it so that crashes by developers weren't counted against release versions. There must be a standard way of doing this.

@davecraig davecraig added the platform Build and release infrastructure label Sep 23, 2024
@davecraig davecraig modified the milestones: urgent, 1.0 Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
platform Build and release infrastructure
Projects
None yet
Development

No branches or pull requests

1 participant