[firebase-crashlytics] Fatal errors aren't sent to Firebase console
還沒有人認領這個 Issue。
評估
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 新手友好度
- 35/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 停滯
- 技術堆疊
- android, firebase, typescript
- 領域
- mobile
研究方向
從 app.ts 中的 Crashlytics 設定以及報告中顯示的 firebase().crashlytics().crash() 呼叫開始。在 Android 上重現致命當機,檢查提供的 Logcat 輸出,並將其與正常運作的 recordError() 路徑進行比較。應用程式重新啟動後,致命當機報告出現在 Firebase 主控台中即表示完成。
由索引模型根據 Issue 內容生成。
描述
Description
On Android, crashing the application with firebase().crashlytics().crash() at launch or on tap of a button doesn't seem to create a report and send it to the Firebase console.
However, non-fatal errors registered using recordError() are logged. Only fatal errors alone are not.
I tried using an emulator as well as a real device.
I didn't encounter this problem on iOS.
I used adb -d shell setprop log.tag.FirebaseCrashlytics DEBUG in order to debug with Android Studio Logcat window.
LOGCAT
When launching the app:
I Initializing Firebase Crashlytics 18.3.5 for [my_app]
D Crashlytics automatic data collection ENABLED by API.
D AnalyticsConnector now available.
D Registered Firebase Analytics listener.
D Could not find resources: 0 0 0
D Mapping file ID is: 00000000000000000000000000000000
D Checking for cached settings...
D Loaded cached settings: {"settings_version":3,"cache_duration":86400,"features":{"collect_logged_exceptions":true,"collect_reports":true,"collect_analytics":false,"prompt_enabled":false,"push_enabled":false,"firebase_crashlytics_enabled":false,"collect_anrs":true,"collect_metric_kit":false,"collect_build_ids":true},"app":{"status":"activated","update_required":false,"report_upload_variant":2,"native_report_upload_variant":2},"fabric":{"org_id":"[my_org_id]","bundle_id":"[my_app]"},"on_demand_upload_rate_per_minute":10,"on_demand_backoff_base":1.2,"on_demand_backoff_step_duration_seconds":60,"app_quality":{"sessions_enabled":true,"sampling_rate":1,"session_timeout_seconds":1800},"expires_at":1692371612723}
D Crashlytics automatic data collection ENABLED by API.
D Opening a new session with ID 64DE3B9F0282000141206C187BCC6F6F
D Successfully configured exception handler.
D Registered Firebase Analytics event receiver for breadcrumbs
D Loaded userId d9cca353b92f4809 for session 64DE3AE602DD00013EC409DA663282C6
D Crashlytics automatic data collection ENABLED by API.
Then, I immediatly click on the crash test button:
E FATAL EXCEPTION: main
Process: [my_app], PID: 16672
java.lang.RuntimeException: Crash Test
at org.nativescript.firebase.crashlytics.FirebaseCrashlytics$Companion.crash$lambda-12(FirebaseCrashlytics.kt:70)
at org.nativescript.firebase.crashlytics.FirebaseCrashlytics$Companion.$r8$lambda$OnmfIXby3H6SMwJX2zdCZGh29Ek(Unknown Source:0)
at org.nativescript.firebase.crashlytics.FirebaseCrashlytics$Companion$$ExternalSyntheticLambda0.run(Unknown Source:0)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:201)
at android.os.Looper.loop(Looper.java:288)
at android.app.ActivityThread.main(ActivityThread.java:7952)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1011)
W at org.nativescript.firebase.crashlytics.FirebaseCrashlytics$Companion.crash$lambda-12(FirebaseCrashlytics.kt:70)
W at org.nativescript.firebase.crashlytics.FirebaseCrashlytics$Companion.$r8$lambda$OnmfIXby3H6SMwJX2zdCZGh29Ek(Unknown Source:0)
W at org.nativescript.firebase.crashlytics.FirebaseCrashlytics$Companion$$ExternalSyntheticLambda0.run(Unknown Source:0)
This follows right after the RuntimeException occured and the error screen on in the app is still visible:
I Initializing Firebase Crashlytics 18.3.5 for [my_app]
D Crashlytics automatic data collection ENABLED by API.
D AnalyticsConnector now available.
D Registered Firebase Analytics listener.
D Could not find resources: 0 0 0
D Mapping file ID is: 00000000000000000000000000000000
D Checking for cached settings...
D Loaded cached settings: {"settings_version":3,"cache_duration":86400,"features":{"collect_logged_exceptions":true,"collect_reports":true,"collect_analytics":false,"prompt_enabled":false,"push_enabled":false,"firebase_crashlytics_enabled":false,"collect_anrs":true,"collect_metric_kit":false,"collect_build_ids":true},"app":{"status":"activated","update_required":false,"report_upload_variant":2,"native_report_upload_variant":2},"fabric":{"org_id":"[my_org_id]","bundle_id":"[my_app]"},"on_demand_upload_rate_per_minute":10,"on_demand_backoff_base":1.2,"on_demand_backoff_step_duration_seconds":60,"app_quality":{"sessions_enabled":true,"sampling_rate":1,"session_timeout_seconds":1800},"expires_at":1692371612723}
D Crashlytics automatic data collection ENABLED by API.
D Opening a new session with ID 64DE3BAD0399000142166C187BCC6F6F
D Successfully configured exception handler.
D Registered Firebase Analytics event receiver for breadcrumbs
D Loaded userId d9cca353b92f4809 for session 64DE3B9F0282000141206C187BCC6F6F
When I restart the app:
I Initializing Firebase Crashlytics 18.3.5 for [my_app]
D Crashlytics automatic data collection ENABLED by API.
D AnalyticsConnector now available.
D Registered Firebase Analytics listener.
D Could not find resources: 0 0 0
D Mapping file ID is: 00000000000000000000000000000000
D Checking for cached settings...
D Loaded cached settings: {"settings_version":3,"cache_duration":86400,"features":{"collect_logged_exceptions":true,"collect_reports":true,"collect_analytics":false,"prompt_enabled":false,"push_enabled":false,"firebase_crashlytics_enabled":false,"collect_anrs":true,"collect_metric_kit":false,"collect_build_ids":true},"app":{"status":"activated","update_required":false,"report_upload_variant":2,"native_report_upload_variant":2},"fabric":{"org_id":"[my_org_id]","bundle_id":"[my_app]"},"on_demand_upload_rate_per_minute":10,"on_demand_backoff_base":1.2,"on_demand_backoff_step_duration_seconds":60,"app_quality":{"sessions_enabled":true,"sampling_rate":1,"session_timeout_seconds":1800},"expires_at":1692371612723}
D Crashlytics automatic data collection ENABLED by API.
D Opening a new session with ID 64DE3BBC002C000142806C187BCC6F6F
D Successfully configured exception handler.
D Registered Firebase Analytics event receiver for breadcrumbs
D No userId set for session 64DE3BAD0399000142166C187BCC6F6F
D Crashlytics automatic data collection ENABLED by API.
I noticed the user ID is missing when I restart the app. I don't know if it matters in this situation.
My app configuration (in app.ts):
firebase().initializeApp().then(() => {
// other configurations for firebase modules
//Crashlytics
firebase().crashlytics().setUserId(device.uuid);
firebase().crashlytics().setCrashlyticsCollectionEnabled(true);
firebase().crashlytics().log('App started');
});
- 主要語言
- TypeScript
- 星號
- 62
- 分支
- 53
- 平均合併
- 7 分鐘
- 30 天內合併 PR
- 1
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
NativeScript/firebase 的其他 Issue
-
難度 3/5 1-2 天 新手友好度 48/100
NativeScript/firebase#292 ·
-
難度 3/5 1-2 天 新手友好度 35/100
NativeScript/firebase#289 ·
-
難度 4/5 3-5 天 新手友好度 35/100
NativeScript/firebase#288 · 4 個 reaction ·
-
[messaging-core][ios] getCurrentToken stalls可能重新可做 @triniwiz 於 190 天前認領,目前沒有進行中的 PR。 未關閉bug ios
NativeScript/firebase#287 · 已指派 1 人 ·
-
Uh-Oh Shazam未關閉
難度 4/5 3-5 天 新手友好度 20/100
NativeScript/firebase#286 ·
查看 NativeScript/firebase 的全部 Issue
相似的 Issue
-
triage
難度 2/5 1-3 小時 新手友好度 75/100
維護者通常 1 天內回覆
-
agent-ready area: config area: skills type: chore upstream: brain-kit
難度 1/5 1 小時以內 新手友好度 95/100
-
enhancement priority:low ready-for-dev
難度 2/5 1-3 小時 新手友好度 75/100
維護者通常 1 天內回覆
-
bug escritorio mapa
難度 2/5 1-3 小時 新手友好度 72/100
marcosferr/reporte-ciudadano#4 · 1 則留言 ·
-
area: material/sort gemini-triaged needs triage
難度 2/5 1-3 小時 新手友好度 70/100
angular/components#33933 ·
維護者通常 1 天內回覆