crashlytics-android

CrashlyticsUploadSymbols for Android native library suceeded but no symbols shown in Firebase console?

*爱你&永不变心* 提交于 2020-06-24 14:51:12
问题 I'm trying to upload native symbols for external native library in Android app. All setup and it seems the crashlyticsUploadSymbolsRelease succeeded. I checked the crashlytics.log and it says that the .cSYM file 's being generated and uploaded to https://cm.crashlytics.com/api/v3/platforms/android/code_mappings. But when I check the Crashlytics tab in the Firebase console the logs are not resolved i.e. no stack traces to be shown. I use LLD as default. I thought that this could be the problem

Firebase crashlytics data not showing up in dashbord even after a day crashlytics was integrated to android app

时光总嘲笑我的痴心妄想 提交于 2020-04-18 06:54:31
问题 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

Build failed with CrashlyticsOrgIdException

亡梦爱人 提交于 2020-04-13 17:14:05
问题 I just integrated the new Firebase SDK following these instructions: https://firebase.google.com/docs/crashlytics/get-started-new-sdk It's working with debug builds, but I get this exception on release build: java.io.IOException: com.google.firebase.crashlytics.buildtools.exception.CrashlyticsOrgIdException: Could not fetch Crashlytics Org Id Any idea? 回答1: I was having the same error when trying to build a release APK, but it wasn't going away. I realized that you need to generate at least

How to effectively group non fatal exceptions in Crashlytics (Fabrics)?

强颜欢笑 提交于 2020-03-14 07:43:02
问题 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

How to effectively group non fatal exceptions in Crashlytics (Fabrics)?

这一生的挚爱 提交于 2020-03-14 07:41:20
问题 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

Firebase Crashlytics Android NDK: empty symbols on crash reports

独自空忆成欢 提交于 2020-02-22 05:28:04
问题 I have a project in Android Studio that consist on Android Java Services that uses some native libraries through JNI calls. Basically, I have 2 libraries I compile and another library that is precompiled, so I don't have access to the source code. As the precompiled library is only built for armeabi-v7a, I have an abiFilter. Here, my /build.gradle // Top-level build file where you can add configuration options common to all sub-projects/modules. buildscript { repositories { google() jcenter()

Firebase Crashlytics does not support NDK?

可紊 提交于 2020-02-05 07:31:04
问题 When you want to use Crashlytics NDK , you need call Fabric.with(this, new Crashlytics(),new CrashlyticsNdk()); But Firebase Crashlytics calls Fabric.with(context, new Kit[]{new Crashlytics()}); on startup. As the result you cannot use Crashlytics NDK. How can I avoid this problem? public class CrashlyticsInitProvider extends ContentProvider { private static final String TAG = "CrashlyticsInitProvider"; public CrashlyticsInitProvider() { } public boolean onCreate() { Context context = this

Crashlytics ndk fails to load

拈花ヽ惹草 提交于 2020-01-20 08:29:30
问题 stepping into crashlytics_init() it is able to do the dlopen() and dlsym() calls to valid addresses. But the sym_ini() call returns null. not sure how do debug why its not loading? there is nothing logged to logcat. Crashlytics crashlyticsKit = new Crashlytics.Builder() .core(new CrashlyticsCore.Builder().disabled(BuildConfig.DEBUG).build()) .build(); Fabric.with(this, crashlyticsKit,new CrashlyticsNdk()); 来源: https://stackoverflow.com/questions/47211657/crashlytics-ndk-fails-to-load

Crashlytics ndk fails to load

孤街浪徒 提交于 2020-01-20 08:29:27
问题 stepping into crashlytics_init() it is able to do the dlopen() and dlsym() calls to valid addresses. But the sym_ini() call returns null. not sure how do debug why its not loading? there is nothing logged to logcat. Crashlytics crashlyticsKit = new Crashlytics.Builder() .core(new CrashlyticsCore.Builder().disabled(BuildConfig.DEBUG).build()) .build(); Fabric.with(this, crashlyticsKit,new CrashlyticsNdk()); 来源: https://stackoverflow.com/questions/47211657/crashlytics-ndk-fails-to-load

Firebase Analytics required for Crashlytics

帅比萌擦擦* 提交于 2020-01-13 19:44:19
问题 I've migrated my apps from Fabric to Firebase. All the apps are now visible in Firebase. My apps don't have Firebase integrated. As per the integration doc, app will still report crashes without Firebase SDK(only need Fabric SDK). What i'm confused about is, do i need to add Firebase Analytics to get proper crash logs ? Because i forced a crash using below code(provided by Firebase) but it didn't record in Firebase but recorded in Fabric. Button crashButton = new Button(this); crashButton