简体   繁体   English

Android 崩溃报告未显示在 Google Play 控制台的 ANR 和崩溃报告中

[英]Android crash reports are not showing up in Google play console's ANRs & Crashes report

I'm currently testing Google play's billing library for in-app subscriptions on my android app.我目前正在我的 Android 应用上测试 Google Play 的应用内订阅计费库。 I've created the subscriptions and have released my app to the internal test track.我已经创建了订阅并将我的应用程序发布到内部测试轨道。 However, when I try going through my billing flow, my app is crashing for an unknown reason.但是,当我尝试完成结算流程时,我的应用程序因未知原因崩溃。 I'm sending the crash report when this happens, but when I look in my android vitals in the ANRs and Crashes report, my crash report data is nowhere to be found.发生这种情况时我正在发送崩溃报告,但是当我在 ANR 和崩溃报告中查看我的 android 生命体征时,我的崩溃报告数据无处可寻。 Instead, Google Console is saying I have "no errors found for the selected criteria".相反,谷歌控制台说我“没有发现所选标准的错误”。


Why is my crash data not registering?为什么我的崩溃数据没有注册? What am I doing wrong here?我在这里做错了什么? I just want to find out where my error is.我只想找出我的错误在哪里。 I have to test my app as a release because otherwise the google billing api won't work.我必须将我的应用程序作为一个版本进行测试,否则 google billing api 将无法工作。 For example, when trying to test on my emulator I get an error response code 5, which says that my application isn't setup for in-app billing.例如,当尝试在我的模拟器上进行测试时,我收到错误响应代码 5,它表示我的应用程序未设置为应用程序内计费。 When testing on the internal testing track, I get past this check and start my billing flow, but then it just crashes.在内部测试轨道上进行测试时,我通过了此检查并开始了我的计费流程,但随后它就崩溃了。


Please help!请帮忙!

Play's Crash Reporting is very delayed. Play 的崩溃报告非常延迟。 It can take 18 hours for a crash log to show up there.崩溃日志可能需要 18 小时才能显示在那里。

Instead, you really should be installing the APK directly on your device and using Android Studio's logcat feature to get the log instantly (filter by Error and search by your app's package name)相反,您真的应该直接在您的设备上安装 APK 并使用 Android Studio 的 logcat 功能立即获取日志(按错误过滤并按您的应用程序包名称搜索)

If you can't do that, then implement Firebase Crashlytics.如果您不能这样做,请实施 Firebase Crashlytics。 Google has a handy guide for you. Google 为您提供了方便的指南 Crashlytics reports are nearly instant. Crashlytics 报告几乎是即时的。

还有一些崩溃,比如永远不会上传到控制台的 TransactionTooLargeException。

Usually, it takes a day or two for the Console to update the statistics.通常,控制台更新统计信息需要一两天时间。 I would recommend using more real-time crash tracking services: Fabric, Firebase.我建议使用更多实时崩溃跟踪服务:Fabric、Firebase。

Another point, a common mistake when testing in-app billing on emulator and getting the另一点,在模拟器上测试应用内计费并获得

application isn't set up for in-app billing应用程序未设置应用程序内结算

error.错误。 Make sure your emulator has Google services installed.确保您的模拟器安装了 Google 服务。 It's usually better to test on a real device.通常最好在真实设备上进行测试。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM