crashlytics

问题 I am using Crashlytics (now known as Fabric) in my app. It works well when the app crashes. I can find the issue on the dashboard. I am trying to use the logging. Something like: Crashlytics.log(Log.WARN,MYTAG,"Error message"); I am not able to send this log in the dashboard. I have just tried to add something like: Crashlytics.logException(new RuntimeException("Fake exception")); but it doesn't send the log. Can Crashlytics send the log? 回答1: You are sending the Log properly. But see what

问题 App crashes when i apply crashlytics on it FATAL EXCEPTION: main Process: com.ehs.pk, PID: 20963 java.lang.RuntimeException: Unable to get provider com.crashlytics.android.CrashlyticsInitProvider: java.lang.ClassNotFoundException: Didn't find class "com.crashlytics.android.CrashlyticsInitProvider" on path: DexPathList[[zip file "/data/app/com.ehs.pk-8.apk"],nativeLibraryDirectories=[/data/app-lib/com.ehs.pk-8, /vendor/lib, /system/lib]] at android.app.ActivityThread.installProvider

问题 Everything works fine when I initialize my application with: Fabric.with(this, new Crashlytics()); However, I get an exception when I use: Fabric.with(this, new CrashlyticsCore()); The following exception: FATAL EXCEPTION: main Process: com.weightbook, PID: 19438 java.lang.IllegalStateException: Crashlytics must be initialized by calling Fabric.with(Context) prior to calling Crashlytics.getInstance() at com.crashlytics.android.Crashlytics.checkInitialized(Crashlytics.java:372) at com

问题 I’ve implemented Crashlytics (2.2.4) in my iOS app for crash report collection. I also implemented another third-party component (Umeng) for other data collection. However, Crashlytics doesn’t send report when Umeng is turned on. When I check the log, there are these suspicious warnings: [Crashlytics] Warning: NSUncaughtExceptionHandler is 'UmengHandleException' [Crashlytics] Warning: sigabrt handler is ‘UmengSignalHandler' [Crashlytics] Warning: sigbus handler is 'UmengSignalHandler'

问题 I’ve implemented Crashlytics (2.2.4) in my iOS app for crash report collection. I also implemented another third-party component (Umeng) for other data collection. However, Crashlytics doesn’t send report when Umeng is turned on. When I check the log, there are these suspicious warnings: [Crashlytics] Warning: NSUncaughtExceptionHandler is 'UmengHandleException' [Crashlytics] Warning: sigabrt handler is ‘UmengSignalHandler' [Crashlytics] Warning: sigbus handler is 'UmengSignalHandler'

问题 This is a screenshot from the duplicated classesWhen I started integrating Digits I had to upgrade Crashlytics after upgrading every time I build the app on pre-Marshmallow Devices I got build Error This one Error:Execution failed for task ':app:transformClassesWithJarMergingForDebug'. com.android.build.api.transform.TransformException: java.util.zip.ZipException: duplicate entry: com/crashlytics/android/answers/shim/AnswersKitEventLogger.class After searching for a while I already tried to .

问题 I've added crashlytics in my app and I've uploaded a build in our private download site which is available for test users. The version which I had uploaded my build used crashlytics version 3.9.0. In my fabric dashboard I was getting crashlog and last crash log was dated last Thu, Nov 9. For past few days(since last friday) I've been getting report from users that they have experienced few crash which they are unable to reproduce and happens occasionally. But when I look at the fabric

问题 Error:A problem occurred configuring root project 'app_name'. > Could not resolve all dependencies for configuration ':_debugCompile'. > Could not find com.crashlytics.sdk.android:answers-shim:0.0.3. Searched in the following locations: https://repo1.maven.org/maven2/com/crashlytics/sdk/android/answers-shim/0.0.3/answers-shim-0.0.3.pom https://repo1.maven.org/maven2/com/crashlytics/sdk/android/answers-shim/0.0.3/answers-shim-0.0.3.aar file:/Users/arun/repos/app_name/libs/answers-shim-0.0.3

问题 I have integrated Crashlytic in reactNative application and tried to check crash logs generated from js files. Its able to capture them but not providing information about the file name. Logs are giving location from index.android.bundle file which are hard to provide any information about crash location. I have already tried react-native-fabric-crashlytics and react-native-fabric npm modules Setting default logger for react native as mentioned in https://www.mojotech.com/blog/fabric

问题 I am receiving multiples crash reports about the same error, but I have no idea what is may causing it. The exception that is throwing is ArrayIndexOutOfBoundsException in android.widget.TextView.makeSingleLayout . I know it is not about Android versions and devices types, since it is getting reports from multiple versions and devices. Here is what I am getting from Crashlytics: Fatal Exception: java.lang.ArrayIndexOutOfBoundsException: length=125; index=-1 at android.text.StaticLayout