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

Get rid of Crashlytics? #427

Open
herzbube opened this issue May 5, 2024 · 0 comments
Open

Get rid of Crashlytics? #427

herzbube opened this issue May 5, 2024 · 0 comments

Comments

@herzbube
Copy link
Owner

herzbube commented May 5, 2024

For a couple of years now Apple has provided crash reports that are directly available in Xcode (Window > Organizer > Crashes). This opens up the question why the app should continue to include a parallel crash reporting infrastructure (Crashlytics)?

=> Analyze what would be the consequences of getting rid of Crashlytics.

If the decision is made to keep the crash reporting infrastructure, then check out out whether Crashlytics can be replaced with plcrashreporter.

Pros at first glance:

  • Open source
  • Clear license
  • Get rid of the opaque (and therefore suspicious) entanglement of Crashlytics with the Google Analytics platform

Cons at first glance:

  • Unclear where to store crash reports submitted by plcrashreporter, and how to symbolicate them.
  • Is it worth replacing one big corp (Google) with another (Microsoft)?
@herzbube herzbube added this to the Soon milestone May 5, 2024
@herzbube herzbube self-assigned this May 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant