crashlytics

Crashlytics Android SDK - custom UncaughtExceptionHandler

爷,独闯天下 提交于 2019-11-27 01:34:30
Is it possible to incorporate custom UncaughtExceptionHandler along with crashlytics in one application? If yes - how? kmityak Since recent versions of Crashlytics perform initialization asynchronously, it's better to use Fabric's initialization callback: private static Thread.UncaughtExceptionHandler mDefaultUEH; private static Thread.UncaughtExceptionHandler mCaughtExceptionHandler = new Thread.UncaughtExceptionHandler() { @Override public void uncaughtException(Thread thread, Throwable ex) { // Custom logic goes here // This will make Crashlytics do its job mDefaultUEH.uncaughtException

How to use Crashlytics with iOS / OS X today view extensions?

岁酱吖の 提交于 2019-11-27 01:04:59
问题 Since today extensions run as separated a process I am sure they will not log any crashes out of the box. I assume we need to initialize Crashlytics on the widget separately. E.g. in the viewDidLoad method of the TodayViewController . Is anybody already using Crashlytics inside any iOS / OS X extensions? If so, how did you implemented it? I am also wondering if it would make sense to create a separate app in Crashlytics just for the extension. 回答1: Crashlytics support got in touch with me and

How to integrate Crashlytics into an iOS framework target?

*爱你&永不变心* 提交于 2019-11-26 21:51:37
问题 I have an iOS framework target, and I need integrate Crash reporting system for it. So Crashlytics looks good, but This Xcode project does not have any Mac or iOS targets So, is there any way to integrate Crashlytics directly into iOS framework? 回答1: Thanks Mike Bonnell for your comment here, which says: Sure, our SDK only supports being initialized once. Being initialized in a framework and application would cause a conflict. You and the app developer would have different API keys and there

How can I fix this CrashlyticsMissingDependencyException?

佐手、 提交于 2019-11-26 19:26:30
问题 I have been using the latest Crashlytics (Fabric integration) for a while. But recently I encountered the following crash error due to missing dependency although I didn't change anything about Crashlytics configurations. any idea? 02-08 22:18:00.935 18887-18887/? E/Fabric﹕ . 02-08 22:18:00.935 18887-18887/? E/Fabric﹕ . | | 02-08 22:18:00.935 18887-18887/? E/Fabric﹕ . | | 02-08 22:18:00.935 18887-18887/? E/Fabric﹕ . | | 02-08 22:18:00.935 18887-18887/? E/Fabric﹕ . \ | | / 02-08 22:18:00.935

Xcode 10b5 - duplicate symbol linker error, can't compile with Crashlytics

久未见 提交于 2019-11-26 18:47:08
问题 I'm trying to compile my project, which has both Firebase, Crashlytics/Fabric, and a bunch of other stuff, with Xcode 10 beta 5. It fails during linking with these errors: Ld /Users/Username/Library/Developer/Xcode/DerivedData/appname-lastnamepjksdzfewpftlvqzuglaxplu/Build/Products/Debug-iphoneos/appname.app/appname normal arm64 (in target: appname) cd /Users/Username/iPhone-dev/appname export IPHONEOS_DEPLOYMENT_TARGET=9.0 /Users/Username/Downloads/Xcode-beta.app/Contents/Developer

Crashlytics: “We're missing a dSYM to process crashes” [closed]

断了今生、忘了曾经 提交于 2019-11-26 18:35:41
Crashlytics says "We're missing a dSYM to process crashes" and when I try to download dSYMs from Xcode (7.1), I get "there are no dsyms available for download" I ran into the same problem today. It seems that iTunes Connect is recompiling apps with bitcode so that the UUID changes, and the dSYM inside the .xcarchive can't actually be used to symbolicate the app (this appears to be a new development). You can download the correct dSYM from iTunes Connect. Login, go to My Apps, select your app, then tap on the Activity tab at the top. Tap on the relevant build, and, assuming the app was

What is causing this Crashlytics compile warning? (Auto-Linking supplied '…' framework linker option at '…' is not a dylib)

江枫思渺然 提交于 2019-11-26 16:20:34
问题 Compiling my main target (not a test target like here) yields this error: ld: warning: Auto-Linking supplied '~/Documents/my_app/MyApp/Crashlytics.framework/Crashlytics', framework linker option at ~/Documents/my_app/MyApp/Crashlytics.framework/Crashlytics is not a dylib From this build command: Ld /Build/Products/Debug-iphonesimulator/MyApp.app/MyApp normal i386 cd ~/Documents/my_app/MyApp export IPHONEOS_DEPLOYMENT_TARGET=8.0 export PATH="/Applications/Xcode.app/Contents/Developer/Platforms

Crashlytics is not sending Crash report from iPhone

无人久伴 提交于 2019-11-26 13:50:07
问题 I've setup the Crashlytics in my one iOS application and installed the application on a real device. My Crashlytics Dashboard is displaying that, I've successfully added the app. However, it's not sending crash report. My internet speed is not so good. But I can check my emails from this device. Can anybody guess, where is the problem? 回答1: Xcode debugger does NOT allow Crashlytics to process crash reports. Yeah, that seem weird even to me when I read that first time but it is a fact (Source)

Crashlytics Android SDK - custom UncaughtExceptionHandler

China☆狼群 提交于 2019-11-26 12:27:57
问题 Is it possible to incorporate custom UncaughtExceptionHandler along with crashlytics in one application? If yes - how? 回答1: Since recent versions of Crashlytics perform initialization asynchronously, it's better to use Fabric's initialization callback: private static Thread.UncaughtExceptionHandler mDefaultUEH; private static Thread.UncaughtExceptionHandler mCaughtExceptionHandler = new Thread.UncaughtExceptionHandler() { @Override public void uncaughtException(Thread thread, Throwable ex) {

How to disable Crashlytics during development

巧了我就是萌 提交于 2019-11-26 10:06:42
问题 Is there any simple way to turn Crashlytics Android SDK off while developing ? I don\'t want it to send a crash every time I do something stupid On the other hand I don\'t want to comment out Crashlytics.start() and possibly risk forgetting to uncomment it and commit 回答1: Marc from Crashlytics here. Here's a couple of ways to disable Crashlytics while you are doing your debug builds! Use a different android:versionString for debug and release builds and then disable crash reporting from the