crashlytics

问题 I added firebase crashlytics to my android app about a day ago. But I still see following getting started guide on the crashlytics page of the firebase console. Following is my git diff for adding crashlytics. project level gradle file: @@ -5,10 +5,12 @@ buildscript { repositories { jcenter() google() + maven { url 'https://maven.fabric.io/public' } } dependencies { classpath 'com.android.tools.build:gradle:3.5.1' - classpath 'com.google.gms:google-services:4.3.0' + classpath 'com.google.gms

问题 Been trying to recreate and research about this issue for days now and I'm not going anywhere. Here's the stack trace. Can anyone shed light on to what's happening? I take that it has something to do with remote notifications. The issue started a while back when I installed the firebase sdk. Back then it wasn't a lot but now, crashes seem to happen more often than usual. Fatal Exception: NSInternalInconsistencyException this request has been neutered - you can't call -sendResponse: twice nor

问题 Expected It is expected for the release version of the Android app's build to run successfully when enabling minifyEnabled and shrinkResources per the Android documentation, Crashlytics, and Proguard. The code for this issue may be found in the open-sourced GitHub repository for Coinverse. Observed The release version of the app crashes immediately when opened after being downloaded from Google Play. This appears to be due to Crashlytics failing to initialize. Without minifyEnabled and

问题 Expected It is expected for the release version of the Android app's build to run successfully when enabling minifyEnabled and shrinkResources per the Android documentation, Crashlytics, and Proguard. The code for this issue may be found in the open-sourced GitHub repository for Coinverse. Observed The release version of the app crashes immediately when opened after being downloaded from Google Play. This appears to be due to Crashlytics failing to initialize. Without minifyEnabled and

问题 I'm found that crash reports became unreadable because of obfuscation. From crashlytics log i'm found exception [DEBUG] (Execution worker for ':') com.crashlytics - POST file: /home/...-875c- 4f7e9d519d53.zip to URL: https://cm.crashlytics.com/api/v3/platforms/android/code_mappings [DEBUG] (Execution worker for ':') com.crashlytics - Crashlytics using custom proxy settings: :80 [WARN] (Execution worker for ':') com.crashlytics - Crashlytics had a problem uploading the deobs file. Please check

问题 I'm found that crash reports became unreadable because of obfuscation. From crashlytics log i'm found exception [DEBUG] (Execution worker for ':') com.crashlytics - POST file: /home/...-875c- 4f7e9d519d53.zip to URL: https://cm.crashlytics.com/api/v3/platforms/android/code_mappings [DEBUG] (Execution worker for ':') com.crashlytics - Crashlytics using custom proxy settings: :80 [WARN] (Execution worker for ':') com.crashlytics - Crashlytics had a problem uploading the deobs file. Please check

问题 I use crashlytics to get the crashes of my app that is in the AppStore. Some users are getting a crash that I cannot seem to repro on my machine (neither the few friends that tested my app through TestFlight). This is the logs from Fabric: Thread : Crashed: com.apple.main-thread 0 libobjc.A.dylib 0x181d09bdc objc_msgSend + 28 1 Foundation 0x18304be20 __NSThreadPerformPerform + 340 2 CoreFoundation 0x182640efc __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 24 3 CoreFoundation

问题 I use crashlytics to get the crashes of my app that is in the AppStore. Some users are getting a crash that I cannot seem to repro on my machine (neither the few friends that tested my app through TestFlight). This is the logs from Fabric: Thread : Crashed: com.apple.main-thread 0 libobjc.A.dylib 0x181d09bdc objc_msgSend + 28 1 Foundation 0x18304be20 __NSThreadPerformPerform + 340 2 CoreFoundation 0x182640efc __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 24 3 CoreFoundation

问题 I'm getting this issue in Crashlytics and, I really don't know what is causing it. It show me that the error is in my AppDelegate, 15 line, but there is where the class beginning: class AppDelegate: UIResponder, UIApplicationDelegate { This is the issue: Fatal Exception: NSInvalidArgumentException Application tried to present modally an active controller RN.ViewController: 0x1509e200. Crashed: com.twitter.crashlytics.ios.exception SIGABRT ABORT 0x00000000206e6c5c 0 RN

问题 We are using Crashlytics in our app as the crash reporting tool. For Android native crashes, it's working fine and grouping the crashes correctly. Our app also has few components in react-native. For the crashes which occur in these components, we catch them and then log them to Crashlytics as non-fatal exceptions. public class PlatformNativeModuleCallExceptionhandler implements NativeModuleCallExceptionHandler { @Override public void handleException(Exception e) { try { . . . Crashlytics