crashlytics

How do I integrate Crashlytics with Android Instant Apps?

廉价感情. 提交于 2019-11-27 14:38:56
Does Crashlytics work with Google Play Instant and if so, how do you setup your project correctly? Yes, Crashlytics does work with Android Instant Apps, in fact it is the recommended crash reporting solution at this stage as it has been tested and works fine. For setup: Step 1 Open the build.gradle file in your base feature module and follow the steps on the public docs site to configure Crashlytics as normal. Step 2 At the top level of your base feature module build.gradle file, add the following Crashlytics flag: ... android { ... } crashlytics { instantAppSupport true } ... Step 3 (optional

Crashlytics deprecated method disabled()

独自空忆成欢 提交于 2019-11-27 14:32:56
问题 When using Crashlytics + Fabric for Android there is a really easy way to enable and disable crash reporting. I use it so during development and testing there aren't a ton of crashes alerting everyone. Crashlytics crashlytics = new Crashlytics.Builder().disabled(true).build(); The disabled(boolean) method is now deprecated. Does anyone know what the replacement is for disabling and enabling crashlytics programmatically? 回答1: Mike from Crashlytics and Fabric here. Here's what you want to use

How to initialize Crashlytics in Fabric.io?

吃可爱长大的小学妹 提交于 2019-11-27 13:38:58
问题 Looking for some help. I just upgraded my android app to fabric and now the app gives an error on this line: Crashlytics.start(getApplicationContext()); Gradle: error: cannot find symbol method start(Context) I tried commenting out that line, but then the crashes are not getting logged. How do I initialize Crashlytics in the new fabric framework? Am I missing something? Thanks in advance for your help. 回答1: Since Crashlytics is now part of Fabric the initialization process has changed, but is

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

点点圈 提交于 2019-11-27 13:24:42
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/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr

Crashlytics not reporting crash in Release mode

◇◆丶佛笑我妖孽 提交于 2019-11-27 13:19:11
问题 Crashlytics has been installed in the app in question for a couple of releases now. It's been working great. But as we prepare the next release Crashlytics has stopped reporting crashes in Release mode. Here are the things I can think of that have changed since our last release. Xcode 7.1. The last release was prepared with Xcode 6. We upgraded to Fabric. We're testing the app on iOS 9.1. Anyway, with all those changes crashes are still being reported just fine in Debug. Just not in Release

How-to find out what causes a didHideZoomSlider error on IOS 8?

纵然是瞬间 提交于 2019-11-27 12:56:11
问题 The following error keeps coming up in my app's crashlytics logs on IOS 8: libobjc.A.dylib objc_msgSend + 5 didHideZoomSlider: Crashed: com.apple.main-thread EXC_BAD_ACCESS KERN_INVALID_ADDRESS at 0x0000000e I have no clue where to start? Anybody an idea on what I should be looking for? The whole stacktrace : 0 libobjc.A.dylib objc_msgSend + 5 didHideZoomSlider: 1 Foundation __NSFireDelayedPerform + 468 2 CoreFoundation __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 14 3

Failed to retrieve settings from https://settings.crashlytics.com/spi/v2/platforms/android/apps/

主宰稳场 提交于 2019-11-27 12:47:37
问题 I am trying out the new Firebase/Crashlytics setup and seem to run into a weird issue. I have one Android code base with multiple product flavors and each flavor is a separate individual app. all of these apps are registered in Fabric (from the past) all of these apps are added in Firebase All linking between the two seems ok (from Fabric side as well as from Firebase side, it says that it is all linked up) I removed the Fabric API key from the manifest file and added the appropriate plugins

Fabric's Crashlytics with Firebase can't be disabled for DEBUG builds

南楼画角 提交于 2019-11-27 11:34:06
问题 I have an app that utilises Fabric's Crashlytics via Firebase. The following is the first thing executed in my Applications onCreate CrashlyticsCore crashlyticsCore = new CrashlyticsCore.Builder() .disabled(BuildConfig.DEBUG) .build(); Fabric.with(this, new Crashlytics.Builder().core(crashlyticsCore).build()); Nonetheless, the crashes are submitted in DEBUG == true mode. I use the following versions in my build.gradle classpath "io.fabric.tools:gradle:1.25.1" in my app/build.gradle

What does transitive = true in Gradle exactly do (w.r.t. crashlytics)?

百般思念 提交于 2019-11-27 10:37:46
What does Gradle transitive = true do exactly? It is not clear from the Gradle documentation . This is in the context of compile within build.gradle . In my case I'm depending Android's crashlytics. compile('com.crashlytics.sdk.android:crashlytics:2.2.2@aar') { transitive = true; } Several Gradle docs ( here and here ) imply that "transitive" defaults to true. Yet removing transitive = true results in transitive dependencies not being brought in (in particular KitGroup ). class file for io.fabric.sdk.android.KitGroup not found The docs say it defaults to true, yet the actual behavior seems to

Crashlytics file not found

自闭症网瘾萝莉.ら 提交于 2019-11-27 09:56:46
问题 Recently opened a project that I had compiled and submitted to Apple. I haven't touched it for a couple of months but I'm getting this odd compile error at: #import <Crashlytics/Crashlytics.h> The error reads: 'Crashlytics/Crashlytics.h' file not found Clearly the framework can't be found but I'm puzzled as to why, when the project was working a few months ago, it's suddenly stopped. Any suggestions why? Xcode: 4.6.3 Mac OS X: 10.8.4 回答1: Just add $(SRCROOT) to the Framework Search Paths in