See attached screenshot (gplay dev console)
v115 was last compiled/upload/published on 4/7/2017 and seemed to be working ok for its first two months.
But on/after 6/7/2017 has been generating many admob-related crashes (w/ no change to app)
I can, of course, release yet another build as of today to blindly check if (aka “hope”) problem might be resolved, but it makes more sense to first ask: is this a known problem, and KNOWN to have been resolved since?
Thanks!
All that I know is that Google has recently changed their crash reporting which has resulted in far more crashes being detected.
Also I believe that particular crash in the screenshot has been fixed.
I’m currently AFK (on mobile) so I can’t verify it at the moment…
i thought the google reporting change was a bit earlier, timing doesn’t quite seem to match (nor do any OTHER errors show a similar increase, which i’d expect if it were just more comprehensive reporting). i guess i was thinking something might’ve changed “server-side” for admob, something that perhaps wasn’t being handled well client-side (but wasn’t “exposed” prior). i rebuilt/repub’d 6/30 after your reply above, just in case – gpdevcon is still empty as of today, but really too early to tell yet. thx
Google changed from reporting only “opt in” ANRs and crashes to everything so expect a large increase in “reported” events
fyi, after a week (-ish) in production (so that new version installs now outnumber previous version), the newly built version hasn’t reported any new occurrences of this specific error, (down from about 100/wk) so it does seem that whatever “fix” may have occurred between ~4/17 and ~6/17 was effective in addressing the issue.
unrelated aside: now if i could just eliminate those darned seg faults in libopenal.so i’d be almost completely crash-free! (other than a very few pesky devices, mainly galaxys, that seem to generate weird ‘random’ crashes on a whim - am ignoring those)
yeah and the random seg faults in libcorona.so too!
All that I know is that Google has recently changed their crash reporting which has resulted in far more crashes being detected.
Also I believe that particular crash in the screenshot has been fixed.
I’m currently AFK (on mobile) so I can’t verify it at the moment…
i thought the google reporting change was a bit earlier, timing doesn’t quite seem to match (nor do any OTHER errors show a similar increase, which i’d expect if it were just more comprehensive reporting). i guess i was thinking something might’ve changed “server-side” for admob, something that perhaps wasn’t being handled well client-side (but wasn’t “exposed” prior). i rebuilt/repub’d 6/30 after your reply above, just in case – gpdevcon is still empty as of today, but really too early to tell yet. thx
Google changed from reporting only “opt in” ANRs and crashes to everything so expect a large increase in “reported” events
fyi, after a week (-ish) in production (so that new version installs now outnumber previous version), the newly built version hasn’t reported any new occurrences of this specific error, (down from about 100/wk) so it does seem that whatever “fix” may have occurred between ~4/17 and ~6/17 was effective in addressing the issue.
unrelated aside: now if i could just eliminate those darned seg faults in libopenal.so i’d be almost completely crash-free! (other than a very few pesky devices, mainly galaxys, that seem to generate weird ‘random’ crashes on a whim - am ignoring those)
yeah and the random seg faults in libcorona.so too!