sentry-cocoa
plcrashreporter
sentry-cocoa | plcrashreporter | |
---|---|---|
2 | 5 | |
766 | 2,827 | |
0.8% | 0.5% | |
9.7 | 8.0 | |
6 days ago | 11 days ago | |
Objective-C | Objective-C | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sentry-cocoa
-
Apple Watch Crash Reporting
Won’t happen until Apple implements exception handling in WatchOS. This issue for Sentry contains a lot of good info on the matter if you’re interested in read more: https://github.com/getsentry/sentry-cocoa/issues/406
-
Random crashes in SwiftUI app?
Is this the message that you've been receiving on Sentry? I have experienced the same. There is an ongoing issue related to this specific message as mentioned here - App hang leads to falsely reported OOM. More details about OOM
plcrashreporter
-
Apple Watch Crash Reporting
Have you tried PLCrashReporter? I haven't tried it on watchOS but it's worth a shot. You'll have to upload the reports to your server manually.
-
Cocoapods, dependencies require me to add framework manually
PLCrashReporter has instructions. We use Swift Package Manager rather than CocoaPods, though.
-
Users keep reporting crashes on my SwiftUI app, but I'm clueless how to investigate them. I'd appreciate any advice or tips!
Recently I integrated PLCrashReporter (https://github.com/microsoft/plcrashreporter) hoping to get a handle on this and I started sending crash reports to the backend.
-
Where do crash reports go for non-appstore apps?
We use PLCrashReporter and upload the crash files manually to our own server on launch.
-
What are all the options for catching user crashes on an iOS app?
I haven't looked at it in depth recently, but depending on what's causing the crash you may not get a crash report. We use PLCrashReporter in our current app and upload the crash report to our server along with the logs the next time the app is launched. Note that you will only get a crash log the next time the app is launched, not immediately after the crash. Doing it manually is a bit of a pain because you have to symbolicate and unique the crash reports yourself.
What are some alternatives?
CocoaLumberjack - A fast & simple, yet powerful & flexible logging framework for macOS, iOS, tvOS and watchOS
ssl-kill-switch2 - Blackbox tool to disable SSL certificate validation - including certificate pinning - within iOS and macOS applications.
ios-crash-dump-analysis-book - iOS Crash Dump Analysis Book
Ramiel - An open-source, multipurpose macOS GUI utility for checkm8-vulnerable iOS/iPadOS devices
nshipster.com - A journal of the overlooked bits in Objective-C, Swift, and Cocoa.
unity - Unity SDK UPM package
Official-Kodi-Remote-iOS - Full-featured remote control for XBMC Media Center. It features library browsing, now playing informations and a direct remote control.
Bugsnag - BugSnag error monitoring & exception reporter for iOS, macOS, tvOS and watchOS
flurry-ios-sdk - Flurry iOS SDK CocoaPods
Examples_Cocoa - Shows how to use macOS AppKit Cocoa controls without StoryBoard only by programming code (objective-c)
SDWebImage - Asynchronous image downloader with cache support as a UIImageView category