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
Crash report #42
Comments
We could use Crashlytics: https://firebase.google.com/docs/crashlytics/customize-crash-reports#add_custom_logs |
That guide is for iOS. Fabrics Crashlytics supported macOS, but Google has given no indication of macOS support for Firebase Crashlytics. I also don't trust Google. |
What about logging the error with SwiftyBeaver? |
That could be an option, but how would we get the logs? We would still have to have them uploaded somewhere. |
I've used their cloud platform, and the Mac app to read logs before. Works pretty good. |
SwiftyBeaver looks good for logging, but it doesn't do automatic crash reporting. I went with Fabric Crashlytics. It's still operational even with the new Firebase Crashlytics. |
This was fixed by 833fd28. |
In Organizer in Xcode, I see some users are getting a crash at:
https://github.com/sindresorhus/gifski-app/blob/eac104f38a1956351d1265b7af7d456c95c31bfc/Gifski/MainWindowController.swift#L124
But there's no error message, so it's hard to guess what the issue is.
This crash has been reported for every version of Gifski since it was first released.
This is what I'm seeing in Xcode:
Is there anything we can do to improve the logging of this error? I assumed
fatalError
would include the actual error message, but it seems not. At least not in the crash report we get from Apple.D3n6t7-Uxh_FcdK-IatJgq.xccrashpoint.zip
The text was updated successfully, but these errors were encountered: