crashlytics

问题 I am getting this error log on crashlytics. I don't know what makes this crash. It occurs on Android 4.x, 5.x, 6.x devices. (Samsung, Sony, LGE etc.) Fatal Exception: java.lang.NullPointerException: Attempt to invoke interface method 'boolean android.view.inputmethod.InputConnection.finishComposingText()' on a null object reference at android.view.inputmethod.InputConnectionWrapper.finishComposingText(InputConnectionWrapper.java:78) at android.view.inputmethod.InputMethodManager

问题 I have a crash in my app. It happens for a lot of users and its multiple places in ActivityThread.java method reportSizeConfigurations. I dont know what this is used for, and why it freezes. The freeze happens right after the splash screen (when the main activity is started) and is only happening on upgrading of the app. If you reinstall the application the problem goes away. Problem is, I cant tell all the users to reinstall the application... Does anyone know what might cause this and why?

问题 I'm trying to automate my app build distribution via Jenkyns and Crashlytics. I configured all as indicated on the documentation but crashlyticsUploadDistributionRelease failed with this error: "Distribution upload failed" and "WARN - Crashlytics halted compilation because it can't distribute the unsigned APK:". how can I fix it ? 回答1: Mike from Fabric and Crashlytics here. Beta for Android only supports distributing a signed APK, unsigned APKs can't be distributed. For information on how to

问题 As the title, I need to migrate all existing data from Fabric's Crashlytics to Firebase. The problem here is after migrating, If I remove fabric key in AndroidManifest, My app can't push the crash report to firebase's Crashlytics anymore. But when I create Firebase's Crashlytics from the beginning (without Fabric migrate) They recommend me to remove existing Fabric key to make it work. Is it ok? 回答1: Mike from Fabric here. Yes, now is a good time to start linking and migrating to Firebase. 来源

问题 Disabling Crashlytics error reporting is relatively straight forward.. I'd also like to disable Answers for debug builds. However, new Crashlytics.Builder().answers(null); doesn't work since apparently answers can't be null and new Crashlytics.Builder().answers(new CustomAnswers()); with CustomAnswers being my class extending Answers gets me a NPE when calling Answers.getInstance() . But that approach is cumbersome to begin with compared to simply calling some enable() method. Any ideas? On a

问题 I'm currently implementing the API Key switching script suggested here, except with build types instead of flavors. My build.gradle looks like this: ... buildTypes { debug { ... set("crashlyticsApiKey", "API_KEY_1") set("crashlyticsApiSecret", "API_SECRET_1") } release { ... set("crashlyticsApiKey", "API_KEY_2") set("crashlyticsApiSecret", "API_SECRET_2") } } ... productFlavors{...} ... File crashlyticsProperties = new File("${project.projectDir.absolutePath}/crashlytics.properties")

问题 I'm currently implementing the API Key switching script suggested here, except with build types instead of flavors. My build.gradle looks like this: ... buildTypes { debug { ... set("crashlyticsApiKey", "API_KEY_1") set("crashlyticsApiSecret", "API_SECRET_1") } release { ... set("crashlyticsApiKey", "API_KEY_2") set("crashlyticsApiSecret", "API_SECRET_2") } } ... productFlavors{...} ... File crashlyticsProperties = new File("${project.projectDir.absolutePath}/crashlytics.properties")

问题 I'm building an iOS app using React Native and trying to get it testable on phones. If I plug my phone into the computer and "build" directly to the phone, the app is built correctly and opens/operates correctly, no problem. But if I try to archive it and send it to phones using iTunes Connect's TestFlight or Fabric with Crashlytics, the app crashes immediately upon opening. It briefly shows the launch screen, but no more. Moreover, there are no crash reports -- in TestFlight, in Crashlytics,

问题 I recently received this app after updating to Crashlytics 3.0 Not sure if it comes from my code or something else. The crash report is untraceable Here is the crash report Crashed: com.apple.main-thread EXC_BAD_ACCESS KERN_INVALID_ADDRESS at 0x000000009a0dbeb8 0 libobjc.A.dylib objc_msgSend + 16 release 1 CoreFoundation CFRelease + 524 2 CoreFoundation -[__NSArrayM dealloc] + 152 3 libobjc.A.dylib (anonymous namespace)::AutoreleasePoolPage::pop(void*) + 564 4 CoreFoundation

问题 I'm trying to get logs with some service data with Crashlytics in my android application. But I don't see my logs in dashboard. I used this: String myLog = getServiceData(); //myLog is not null and non-empty CrashLytics.log(myLog); and this: String myLog = getServiceData(); //myLog is not null and non-empty CrashLytics.log(Log.Error, getString(R.string.app_name), myLog); I tried to generate exception in my application and handle it, but have no results: try { int a = 0; a = 1/a; } catch