google-fabric

Old Fabric app won't show crashes on new Firebase implementation

て烟熏妆下的殇ゞ 提交于 2021-02-11 17:52:25
问题 I have implemented Firebase/Crashlytics to an app. I can see in the logs that app is sending crashes. Firebase Console doesn't show anything. I can see crash free user count decreased after the implementation. Console doesn't show up anything. Please help. My app ID: com.obssmobile.mychesspuzzlegame I have disconnected the Xcode debugger, relaunched the app and remade the crashes. Issue is persisting. Here I can see that crash free users started dropping. Here I can see "report submission

How to export crash-free users from firebase?

旧街凉风 提交于 2021-01-27 14:22:23
问题 I want to persist data about crashes and metrics of crash-free users in my database for further analyze. I have already linked the project to BigQuery, but can't find a way to calculate crash-free users value by data, which contained in BigQuery. It's possible to export crash-free users metrics in some way? 回答1: Fabric/Firebaser here - The Firebase Crashlytics export to BigQuery doesn't include crash-free users because Google Analytics for Firebase is needed to calculate the crash-free users

E/FirebaseCrashlytics: Failed to retrieve settings from https://firebase-settings.crashlytics.com/spi/v2/platforms/android/gmp/XXXX/settings

爷,独闯天下 提交于 2021-01-21 12:12:32
问题 I tried new Firebase Crashlytics SDk after migrating from Fabric and seem to run into a weird issue. Crash logs are not captured in dashboard after upgrading firebase-crashlytics to 17.0.0 and I get this error in log: E/FirebaseCrashlytics: Failed to retrieve settings from https://firebase-settings.crashlytics.com/spi/v2/platforms/android/gmp/XXXX/settings and I followed all instructions from firebase console quickstart guide. Please help me if any one have faced similar issue. 回答1: In my

E/FirebaseCrashlytics: Failed to retrieve settings from https://firebase-settings.crashlytics.com/spi/v2/platforms/android/gmp/XXXX/settings

空扰寡人 提交于 2021-01-21 12:12:09
问题 I tried new Firebase Crashlytics SDk after migrating from Fabric and seem to run into a weird issue. Crash logs are not captured in dashboard after upgrading firebase-crashlytics to 17.0.0 and I get this error in log: E/FirebaseCrashlytics: Failed to retrieve settings from https://firebase-settings.crashlytics.com/spi/v2/platforms/android/gmp/XXXX/settings and I followed all instructions from firebase console quickstart guide. Please help me if any one have faced similar issue. 回答1: In my

E/FirebaseCrashlytics: Failed to retrieve settings from https://firebase-settings.crashlytics.com/spi/v2/platforms/android/gmp/XXXX/settings

杀马特。学长 韩版系。学妹 提交于 2021-01-21 12:08:58
问题 I tried new Firebase Crashlytics SDk after migrating from Fabric and seem to run into a weird issue. Crash logs are not captured in dashboard after upgrading firebase-crashlytics to 17.0.0 and I get this error in log: E/FirebaseCrashlytics: Failed to retrieve settings from https://firebase-settings.crashlytics.com/spi/v2/platforms/android/gmp/XXXX/settings and I followed all instructions from firebase console quickstart guide. Please help me if any one have faced similar issue. 回答1: In my

Permission denied with Firebase distribution android app using service account credentials mode

半城伤御伤魂 提交于 2020-12-26 08:33:09
问题 I'm trying to migrate from Fabric to Firebase since Fabric will not be available beyond March 31, 2020. I already have done the first steps: adding plugins and dependencies to gradle, adding analytics json file, even crash reporting, and all seems correct because I can see data in the Firebase console (analytics and crashes). But I'm not so lucky migrating the app distribution system from Beta+Fastlane to Firebase. I'm trying the option " Distribute Android apps to testers using Gradle ". I

How to migrate from Fabric Crashlytics to Firebase Crashlytics?

余生颓废 提交于 2020-12-08 05:49:47
问题 I have an app that logs crashes and non-fatals to Fabric Crashlytics and uses Firebase Analytics to log analytics events. I want to migrate from Fabric Crashlytics to Firebase Crashlytics. In addition I want to save historical data from Fabric during the migration. When I try to do it with provided mechanism of Firebase Migration (https://fabric.io/firebase_migration/apps) I cannot do it in a way I want to. In particular, I cannot provide existent Firebase project ID for migration. I see

How to migrate from Fabric Crashlytics to Firebase Crashlytics?

末鹿安然 提交于 2020-12-08 05:48:03
问题 I have an app that logs crashes and non-fatals to Fabric Crashlytics and uses Firebase Analytics to log analytics events. I want to migrate from Fabric Crashlytics to Firebase Crashlytics. In addition I want to save historical data from Fabric during the migration. When I try to do it with provided mechanism of Firebase Migration (https://fabric.io/firebase_migration/apps) I cannot do it in a way I want to. In particular, I cannot provide existent Firebase project ID for migration. I see

iOS Firebase Crashlytics not showing up crashes in Dashboard

前提是你 提交于 2020-11-28 08:57:26
问题 I implemented Firebase Crashlytics in my iOS app. I followed all the steps in firebase documentation. I already ran crashlytics without the debugger by closing the app first and then re run the app so that crash reports can be sent. I even get this message Crash upload submission succesful I even added the Run script and set variable to "DWARF with DSYM" "${PODS_ROOT}/Fabric/run" I ready somewhere that if DSYM aren't uploaded you won't see your crashes even if they are uploaded successfully.

iOS Firebase Crashlytics not showing up crashes in Dashboard

♀尐吖头ヾ 提交于 2020-11-28 08:57:22
问题 I implemented Firebase Crashlytics in my iOS app. I followed all the steps in firebase documentation. I already ran crashlytics without the debugger by closing the app first and then re run the app so that crash reports can be sent. I even get this message Crash upload submission succesful I even added the Run script and set variable to "DWARF with DSYM" "${PODS_ROOT}/Fabric/run" I ready somewhere that if DSYM aren't uploaded you won't see your crashes even if they are uploaded successfully.