crashlytics

问题 I added firebase crashlytics dependencies to my project and after that the project does not build. https://firebase.google.com/docs/crashlytics/get-started?authuser=0&platform=android#android Could you please suggest on what I might be doing wrong. Thanks R Build fails on these lines implementation "com.google.android.gms:play-services-base:17.0.0" implementation 'com.google.firebase:firebase-core:17.0.0' This is the error log Task :app:processDebugManifest FAILED C:\Development\xxx\xxx-app

问题 I intentionally crashed my application when there was no WIFI to check whether the crash report is updated in Crashlytics and it didn't get updated as there was no WIFI. But when i turned on the wifi the crash didn't get reported. But if i again crash my application when the wifi is switched on. The crash report for this crash along with the crash which occurred when the wifi was off got updated. I'm not able to figure out the reason behind it. Any help would be appreciated. 回答1: Marc from

问题 Does Crashlytics work with Google Play Instant and if so, how do you setup your project correctly? 回答1: 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

问题 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

问题 I develop app in xcode 6. And then device connected i run app with debug. After i can disconnect device from xcode and again run app. And it's runs. But today begins some problems i run app with run button in xcode 7 -> app run normally, and work good. After i disconnect device from my mac, and try run app by press app icon on device and got crash Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Triggered by Thread: 0 Thread 0 name: Dispatch queue:

问题 I updated Android Studio to 2.0 and trying to get instant run to work. Gradle sync works. Rebuilding the project works. Trying to run, fails :(. What am I doing wrong? Variables: io.fabric.tools:gradle:1.14.4 com.android.tools.build:gradle:2.0.0-alpha1 buildToolsVersion 23.0.2 Error: FAILURE: Build failed with an exception. What went wrong: Could not determine the dependencies of task ':Application:crashlyticsStoreDeobsDebug'. Task with path 'dexDebug' not found in project ':Application'. Try

问题 I've been having an issue and I don't know how to fix it. My project use crashlytics, but it's always crash and not sent report. I have a TimeoutException: 08-25 03:04:31.876 2856-2856/connectivit.app E/Fabric﹕ Failed to execute task. java.util.concurrent.TimeoutException at java.util.concurrent.FutureTask.get(FutureTask.java:176) at com.crashlytics.android.core.CrashlyticsExecutorServiceWrapper.executeSyncLoggingException(CrashlyticsExecutorServiceWrapper.java:44) at com.crashlytics.android

问题 I was wondering if it is possible to somehow view all the crashes (or non-fatals) for a particular issue from the Crashlytics dashboard. Even though the exception is logged in the same place in the code, the stack trace and exception type/message may be different. But since the exception is logged in the same place, Crashlytics treats it as the same issue. As far as I can tell, you can only view the latest crash or non-fatal. Is there a way? Or alternatively, are there Crashlytics SDK calls

问题 What is an effective way of segregating dev builds in Crashlytics? We are currently appending the letter "D" onto our development builds, and then using the "Hidden Versions" feature in the Crashlytics app settings to turn off any versions that have "D" in them. It's a manual step, so it's not great. It also doesn't work entirely - I still see "D" versions showing up in some Crashlytics UI, like the version adoption box. What solution has the Crashlytics community decided is best? 回答1: Mike

问题 We're using Fabric / Crashlytics for sending non-crash issues to their servers and later checking out the logs and stacktraces. Unfortunately, the Crashlytics API requires to use a different Exception subclass instance for different issue types. (In the iOS SDK, you can simply use a string for different issue types, but in the Android version, you can't). public static void craslyticsRecordError(String issueType, String errorMsg) { Exception e = new Exception(issueType + "-" + errorMsg);