Can't get crash log from emulator

[AOEGame]

[READ] For Firebase Unity SDK issues, please report to Firebase Unity open-source

Once you've read this section and determined that your issue is appropriate for this repository, please delete this section.

[REQUIRED] Please fill in the following fields:

• Unity editor version: 2020.3.27f
• Firebase Unity SDK version: 9.1.0
• Source you installed the SDK: .unitypackage
• Problematic Firebase Component: Crashlytics
• Other Firebase Components in use: Analytics, CloundMessing
• Additional SDKs you are using: None
• Platform you are using the Unity editor on: Windows
• Platform you are targeting: iOS, Android
• Scripting Runtime: IL2CPP

[REQUIRED] Please describe the issue here:

I can't get crash log from emulator. MUMU Emulator Android version: 6.0.1

Steps to reproduce:

use code: UnityEngine.Diagnostics.Utils.ForceCrash(UnityEngine.Diagnostics.ForcedCrashCategory.AccessViolation); or UnityEngine.Diagnostics.Utils.ForceCrash(UnityEngine.Diagnostics.ForcedCrashCategory.Abort);

Force Crash.

I can't get crash log from emulator. (MUMU Emulator).

I can get crash log from android phone.

[paulinon]

Hi @AOEGame,

Thanks for reporting this issue. While I try to replicate this on my end, I'd like you to perform a few tests:

• Could you verify if the issue persists using SDK version 9.4.0?
• Are you able to receive crash logs from other MuMu emulators with a higher Android version? If not, please specify the Android versions used.
• Is the behavior reproducible using other emulators (like ones from Android Studio)?

I look forward to your results.

[google-oss-bot]

Hey @AOEGame. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[google-oss-bot]

Since there haven't been any recent updates here, I am going to close this issue.

@AOEGame if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.