High rate of ANRs on Android

Report · May 11, 2018

There are posts about this issue dating back years - the only replies from Adobe are either asking the poster to file a bug report (these have been filed) or, less helpfully, explaining to the poster what an ANR is (nice) and just telling them it's probably their fault.

Has anyone at Adobe ever investigated this issue in earnest, in order to definitively rule out the possibility that it could be at least in part an issue with AIR and not the fault of the developer? It's happening to many users and being discussed several places, and it's become a critical issue now that Google is aggressively punishing apps' discoverability as a result.

Tracker

https://github.com/Gamua/Adobe-Runtime-Support/issues/29#issuecomment-388067899

https://forum.starling-framework.org/topic/anrs-crash-rate-survey

I'm finding it a bit of a stretch to believe that all of these developers are simply piling too much inefficient code in their touch-event handlers, but I'd be happy to be proven wrong. Any thoughts?

Report · May 22, 2018

It looks like this might be a deadlock in sound playback code? Developers are reporting success using ANEs to play all sounds on Android to get rid of the ANRs: https://github.com/Gamua/Adobe-Runtime-Support/issues/29#issuecomment-390884726