Android 市场崩溃报告未使用 bugsense 进行报告
我最近在 Android 市场上收到了我的一个应用程序的 NullPointerException 崩溃报告。我在测试时无法重现该错误，因此我认为它可能特定于某个设备。为了解决这个问题，我在最新版本中包含了 BugSense。 BugSense 一直致力于报告其他问题并且非常有帮助，但我仍然收到 Android Market 中但 BugSense 中的最新版本的原始错误报告。 BugSense 在某些设备上不起作用吗？
有关崩溃的一些详细信息：
- 在我的启动屏幕活动中调用了 BugSense。
- 启动画面打开主活动。
- 主 Activity 有一个 MyObject 实例。
- 当用户单击 ListView 中的项目时，将设置 MyObject。
- 单击 ListView 中的某个项目将打开一个 AlertDialog。
- MyObject.getName() 在 onCreateDialog 中调用。
- 发生崩溃 - NPE。
BugSense 仪表板上不会出现错误。 Android 市场中的用户评论指出“应用程序一打开就崩溃了”。我最初的想法是用户找到了一种无需单击列表项即可打开对话框的方法，但在看到用户评论后，应用程序似乎在需要调用 onCreateDialog 之前尝试访问它。
所以我的问题是：应用程序怎么可能在没有 BugSense 报告的情况下崩溃？为什么 onCreateDialog 会在 Activity 需要它之前被调用？
I recently was receiving a NullPointerException crash report in the android market with one of my apps. I was not able to recreate the bug when testing so I thought it may be specific to a device. To solve this issue I included BugSense with my latest release. BugSense has worked reporting other issues and has been very helpful, but I am still getting reports of the original error with the latest version in the Android Market but in BugSense. Does BugSense not work on some devices?
Some details about the crash:
- BugSense is called in my Splash Screen Activity.
- Splash Screen opens the Main Activity.
- Main Activity has an Instance of MyObject.
- MyObject is set when a user clicks an item in a ListView.
- Clicking an item in the ListView opens an AlertDialog.
- MyObject.getName() is called in onCreateDialog.
- Crash Occurs - NPE.
Error doesn't appear on BugSense Dashboard. User Comments in Android Market state "app is crashing as soon as it opens." My original thought was the user found a way to open a dialog without clicking on a list item but after seeing the user comment it appears the app is trying to access onCreateDialog before it ever needs to be called.
So my questions: How is it possible for the app to crash without BugSense reporting on it? and Why would onCreateDialog get called before the Activity ever needs it?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我使用 ACRA 报告崩溃，并将其上传到 Google Docs（“正常”ACRA 方式）和 BugSense。
即使在与 BugSense 交换了多封电子邮件并尝试解决问题之后，我在 Google Docs 中收到的条目数量仍然是 BugSense 中条目数量的 5 倍。
BugSense 悄悄地丢弃了五分之四的报告，很可能是因为它的解析器不喜欢报告中包含的数据。它的 UI 比浏览庞大的 Google Docs 电子表格有用得多，但我不能相信 BugSense，因为它报告的内容太少了。
I use ACRA to report crashes, and upload them to both Google Docs (the "normal" ACRA way) and BugSense.
Even after exchanging multiple emails with BugSense, and their attempts to fix the situation, I get about 5 times the number of entries in Google Docs than I get in BugSense.
BugSense is silently dropping 4 in 5 reports, most likely because its parsers don't like the data that the reports contain. Its UI is much more useful than wading through a huge Google Docs spreadsheet, but I can't trust BugSense because it under-reports so much.
嗯，如果您使用 ACRA 或 Crittercism？
hmm do you get the crash if you use ACRA or Crittercism?