crashlytics-android | 易学教程

Crashlytics NDK symbols and Gradle tasks

阅读更多关于 Crashlytics NDK symbols and Gradle tasks

问题 I have a question that mostly relates to gradle. I'm using Crashlytics to report NDK crashes in my Android app. I have a task in build.gradle that calls ndk-build and compiles the cpp files into an .so file. At the end of this task I want to call a task that uploads generated symbols mapping to Crashlytics. After installing the Fabric plugin in Android Studio, I saw there are some new tasks that were added to the Gradle tab. One of them is crashlyticsUploadSymbols[buildType][flavour] where

Crashlytics says “Received null settings, skipping report submission”

阅读更多关于 Crashlytics says “Received null settings, skipping report submission”

问题 I am trying to switch from Firebase Crash reporting to Firebase Crashlytics. I have followed the guide here: https://firebase.google.com/docs/crashlytics/upgrade-from-crash-reporting But during initialization the logs says: Received null settings, skipping report submission! And then when testing crashes: Cannot send reports. Settings are unavailable. Network connection is good, so no reason why it can't get settings. Log output: D/CrashlyticsCore: Initialization marker file created. W

Fabric Beta and APK splits

阅读更多关于 Fabric Beta and APK splits

I'm splitting my app based on ABI, not on density, like so: splits { abi { enable true reset() include 'x86', 'armeabi', 'armeabi-v7a', 'mips', 'arm64-v8a' universalApk true } } I have multiple flavors, and 2 build types (debug and release). I want to put the universal apk file, that has native libs for all platforms, up on fabric beta. From what I understand, this is supported through the ext.betaDistributionApkFilePath attribute. I can define this either at the buildType level, or at the flavor level. The problem is I need both build type and flavor to pick up my variant - something like

How do I use Crashlytics for my React Native Android App?

阅读更多关于 How do I use Crashlytics for my React Native Android App?

问题 I am trying to figure out how to use Crashlytics from Fabric for my React Native Android APP. I followed the steps on the Fabric homepage and added some lines in my build.gradle files. But the builds always crash. Is there a difference using Crashlytics for React Native Android and Crashlytics for Native Android development using Android Studio and Java? 回答1: I got it working in some way, but it may not be the perfect solution... 1: Add fabric/crashlytics into your app/build.gradle - File (I

Can't disable Crashlytics in a Firebase app (anymore)

阅读更多关于 Can't disable Crashlytics in a Firebase app (anymore)

问题 After upgrading to com.crashlytics.sdk.android:crashlytics:2.7.1@aar (from 2.6.8), I can't disable Crashlytics anymore in my Firebase app. Looks like there's some code in Crashlytics library itself that initializes Fabric with Crashlytics kit enabled whenever it detects that it's running inside a Firebase application. Indeed initializing with Crashlytics enabled and with ext.enableCrashlytics = false throws an UnmetDependencyException and crashes the app at startup (in fact, before my code in

ERROR: No signature of method: com.crashlytics.tools.gradle.CrashlyticsPlugin.findObfuscationTransformTask()

阅读更多关于 ERROR: No signature of method: com.crashlytics.tools.gradle.CrashlyticsPlugin.findObfuscationTransformTask()

问题 I am getting the following error while trying to build my project on Android Studio: ERROR: No signature of method: com.crashlytics.tools.gradle.CrashlyticsPlugin.findObfuscationTransformTask() is applicable for argument types: (java.lang.String) values: [DevDebug] How to solve this? 回答1: This seems to be an issue related to version "1.28.0" of "io.fabric.tools:gradle" . Usually this kind of problem occurs if groupId:artifactId:n.+ structure of versioning is used inside dependency (app level

How do I use Crashlytics for my React Native Android App?

阅读更多关于 How do I use Crashlytics for my React Native Android App?

I am trying to figure out how to use Crashlytics from Fabric for my React Native Android APP. I followed the steps on the Fabric homepage and added some lines in my build.gradle files. But the builds always crash. Is there a difference using Crashlytics for React Native Android and Crashlytics for Native Android development using Android Studio and Java? I got it working in some way, but it may not be the perfect solution... 1: Add fabric/crashlytics into your app/build.gradle - File (I didn´t have the buildscript in my app/build.gradle so i just included it. But i am not sure if this is good.

Can't disable Crashlytics in a Firebase app (anymore)

阅读更多关于 Can't disable Crashlytics in a Firebase app (anymore)

After upgrading to com.crashlytics.sdk.android:crashlytics:2.7.1@aar (from 2.6.8), I can't disable Crashlytics anymore in my Firebase app. Looks like there's some code in Crashlytics library itself that initializes Fabric with Crashlytics kit enabled whenever it detects that it's running inside a Firebase application. Indeed initializing with Crashlytics enabled and with ext.enableCrashlytics = false throws an UnmetDependencyException and crashes the app at startup (in fact, before my code in Application.onCreate runs). Does anyone know a workaround for that? Sticking with 2.6.8 works for now.

Collect logs from system classes

阅读更多关于 Collect logs from system classes

问题 I'm working on an app that uses Android's MediaMuxer for recording the screen. Using Crashlytics, a significant number of users have the "Failed to stop the muxer" crash, but I can't reproduce it locally on any of my devices. According to another question, the MPEG4Writer logs generated while MediaMuxer is running should indicate what the source of the problem is, but since I'm unable to reproduce it locally, I need to collect those logs remotely and pass them over to Crashlytics. So here's

Collect logs from system classes

阅读更多关于 Collect logs from system classes

I'm working on an app that uses Android's MediaMuxer for recording the screen. Using Crashlytics, a significant number of users have the "Failed to stop the muxer" crash, but I can't reproduce it locally on any of my devices. According to another question , the MPEG4Writer logs generated while MediaMuxer is running should indicate what the source of the problem is, but since I'm unable to reproduce it locally, I need to collect those logs remotely and pass them over to Crashlytics. So here's my problem: MediaMuxer and MPEG4Writer are system classes, so obviously I can't edit them to add