Open jeffkelsey opened 7 years ago
Thanks for this report. I am quite surprised to see it.
Reviewing the code, it seems for this crash to happen a previously initialized variable must have mysteriously become null, something I believe should be impossible.
Do you see this with any specific devices or OS versions?
Seems to be across most devices and versions: of the 1209 CRASHES 1210 USERS:
Devices samsung 81% LGE 7% motorola 4% Other… 8%
OS: Operating Systems 6 84% 5 7% 4 7% Other 2%
Hi @davidgyoung,
I have the same crash as jeffkelsey when I use this class in some devices.
Did you had the chance to review this?
Best,
Chema
Since I cannot reproduce this problem or even explain how it could happen, the best I can do is protect against a crash by adding a null check in the next version. I'll put this in the next release.
Thanks for your effort!!
Best,
Chema.
Is there a release that has this fix included or a timeline for next release? This is still the top crasher in our production application.
@jeffkelsey how would you feel about putting a prerelease with this fix into your app? If so I can make you a special build with the latest release binary and only this change for you to deploy and see if these crashes go away.
It is a low risk change. But I am reluctant to put this in a full release since I have no way to reproduce or test that it helps.
That works for me
On Feb 28, 2017 1:55 PM, "David G. Young" notifications@github.com wrote:
@jeffkelsey https://github.com/jeffkelsey how would you feel about putting a prerelease with this fix into your app? If so I can make you a special build with the latest release binary and only this change for you to deploy and see if these crashes go away.
It is a low risk change. But I am reluctant to put this in a full release since I have no way to reproduce or test that it helps.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/AltBeacon/android-beacon-library/issues/469#issuecomment-283173226, or mute the thread https://github.com/notifications/unsubscribe-auth/AGXC6Pp2GjCgdSi0tw5YvkIQY3wg1meFks5rhJfqgaJpZM4LgHwF .
How can you send me the pre-release? We have a new build getting ready to RC test on Monday and I would love to get this in before then
@jeffkelsey, I have prepared a release with instructions here: https://github.com/AltBeacon/android-beacon-library/releases/tag/fix-power-saver-crash
Please give this a try and let me know how it affects these crash reports.
This may be a symptom of a problem with singleton object creation fixed in #494.
Expected behavior
No crash reports
Actual behavior
Top 2 crashers in our app based on Fabric data is:
Crash 1:
Crash 2:
Mobile device model and OS version
Android Beacon Library version
2.5.1 used within the ExactTarget 4.7.1 sdk (example in https://github.com/salesforce-marketingcloud/LearningAppAndroid/blob/master/app/build.gradle)