crashlytics

问题 I need to export the Crashlytics Crashes Report Log into some external file system. Using their hooks will not work as those are only for new reports whereas I need to export the full open issues. I have found this library: https://github.com/MattNewberry/crashstats but it seems that Crashlytics are blocking it from working. Looking at the chrome debugger, I am trying to replicate the call to their API using curl so I can later code it in Java/ Ruby: $ curl --data "email=user@example.com

问题 After upgrading from Android Gradle Plugin 3.2.0 to 3.3.0-alpha13 , I'm seeing the following build error: > Task :app:fabricGenerateResourcesDebug FAILED ERROR - Crashlytics Developer Tools error. java.lang.IllegalArgumentException: Crashlytics found an invalid API key: null. Check the Crashlytics plugin to make sure that the application has been added successfully! Contact support@fabric.io for assistance. It appears that the processDebugGoogleServices task is no longer running before the

问题 I'm using the latest version of the Fabric and Fabric/Crashlytics cocoapods (so, version 3.0.8 according to the debugger output) to integrate Crashlytics into an iOS keyboard extension. Recently, it simply stopped reporting crashes from the keyboard extension. I've checked both my code which initializes Crashlytics and the Crashlytics script build phase of my project, both are executed (and the build phase is in my keyboard extension's target). It's hard to tell if this is related, but when I

问题 I set up a firebase project with crashalytics and I can see Java and NDK crashes on the Dashboard. I am trying to upload symbols as per https://firebase.google.com/docs/crashlytics/ndk-reports#upload_native_symbols. I also tried following blogs like https://medium.com/@aungkyawmyint_26195/setting-up-ndk-crashlytics-android-11ad775676f7, but have been unsuccessful so far. Here is my environment Android Studio 3.5 Build #AI-191.8026.42.35.5791312, built on August 8, 2019 JRE: 1.8.0_202-release

问题 I'm developing an Andriod SDK project, intended to be imported by other applications. Currently I have Crashlytics integrated in my SDK. The problem is that some of our clients who want to use the SDK already have Crashlytics integrated, which causes a conflicts between the two fabric libraries. Is there a way to have Crashlytics installed in an SDK and in its embracing app? 来源： https://stackoverflow.com/questions/30444744/android-installing-crashlytics-in-an-sdk-and-its-embracing-app

问题 I'm investigating how to create a server side iOS crash report symbolication server like Crashlitics or Crittercism or HokeyApp, from I can see, they only ask the user to upload the .dSYM file then they are able to symbolicate the crash report, I'm wondering how they archive it? Apple's standard symbolicatecrash command needs the app binary and the .dSYM file being provided together: Symbolication - resolving stack trace addresses to source code methods and lines - requires the application

问题 I am using the Crashlytics in order to report the crash occurs in the iOS app. Here, I want to know how to find the path of these below dwarf folder and file in xcode: DWARF_DSYM_FOLDER_PATH DWARF_DSYM_FILE_NAME 回答1: You need to go to Organizer and select your archive file, select show in finder after that you need to select show package content and finally there is your DYSM folder 回答2: You can do it using xcodebuild tool: xcodebuild -project MyProject.xcodeproj -target MyTarget

问题 I am building an android library that I plan to integrate into many 3rd party apps(which do not belong to me). So, I am trying to figure out a way to find out if any of those 3rd party apps crashes due to the code in my library. Is there any way to find that out? I was looking at Crashlytics to achieve the same. But, as I understand, Crashlytics will be able to give the Crash analytics to only the app owner, right? Is there any way to collect the crash info without the intervention of the 3rd

问题 I have been trying to build the application which uses crashlytics from fabric.io. But build gets failed with bellow mentioned error. Executing tasks: [clean, :app:generateDebugSources, :app:generateDebugAndroidTestSources] Configuration on demand is an incubating feature. FAILURE: Build failed with an exception. * What went wrong: A problem occurred configuring project ':app'. > Could not resolve all dependencies for configuration ':app:classpath'. > Could not resolve io.fabric.tools:gradle

问题 According to Fabric documentation Fabric doc to reduce user traffic, caught exceptions are sent only when the app launches - Crashlytics processes exceptions on a dedicated background thread, so the performance impact to your app is minimal. To reduce your users’ network traffic, Crashlytics batches logged exceptions together and sends them the next time the app launches. try { myMethodThatThrows(); } catch (Exception e) { Crashlytics.logException(e); // handle your exception here! } But for