Closed lklong1551019 closed 3 months ago
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
Hi @lklong1551019, thank you for reporting the issue. This issue seems related to the issue #6001 you reported. I have raised this issue to our engineers and are already taking a look. Please hang tight!
thank you, glad to hear that. I'm looking forward to hearing updates, cheers.
I'll be closing this thread now. To streamline the updates from our engineer, moving forward, you can check on the issue #6001. Thanks!
[READ] Step 1: Are you in the right place?
Issues filed here should be about bugs in the code in this repository. If you have a general question, need help debugging, or fall into some other category use one of these other channels:
[REQUIRED] Step 2: Describe your environment
Android Studio version:
Android Studio Jellyfish | 2023.3.1 Patch 1 Build #AI-233.14808.21.2331.11842104, built on May 15, 2024 Runtime version: 17.0.10+0-17.0.10b1087.21-11572160 aarch64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o. macOS 14.5 GC: G1 Young Generation, G1 Old Generation Memory: 4096M Cores: 8 Metal Rendering is ON Registry: ide.instant.shutdown=false debugger.new.tool.window.layout=true ide.experimental.ui=true ide.images.show.chessboard=true Non-Bundled Plugins: io.github.stefansjs.flatbuffersplugin (0.5+31) name.kropp.intellij.makefile (233.13135.65)
Firebase Component: com.google.gms:google-services:4.4.1, com.google.firebase:firebase-crashlytics-gradle:2.9.9, org.jetbrains.kotlin:kotlin-gradle-plugin:1.9.21, com.google.firebase:firebase-bom:32.8.0
Component version: org.jetbrains.kotlin:kotlin-gradle-plugin:1.9.21
[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
After updating firebase bom from 31.2.3 to 32.8.0, for the past few days we have been experiencing random crashes (~ 7 crashes per day on avg) on a variety of devices, across every android version (58% android 13), with 95% events happened while in background. It happened on app start, eg, the first 5 seconds.
We cannot reproduce this. Here is an example stack trace:
Is there anything we could do? Any insight would be appreciated.