Copy link to clipboard
Copied
Hi Adobe team,
over the last months the developer community has been discovering an issue that causes freezes (ANRs) in Air apps. Since Google recently changed the visibility algorithms for Google Play to punish apps that show high quotas of faulty behavior, all Air apps are now directly affected by this punishment.
We believe that we have been able to narrow the problem down to playing sounds in an Air application. Developers report those ANRs both for streaming sounds as well as playing sounds locally. Specifically, our company has been able to reliably reproduce the freeze by creating a bot that will play our game over a lengthy session. After 1-3 hours, the app will just freeze. If we disable the sound, the freeze will not occur. Furthermore, if we endlessly loop a single sound instance with a volume of 0, the freeze also does not occur. However this workaround causes wake locks because the device can never go to full sleep even when the user puts it into background, since the sound still plays. Wake locks are also punished by Google Play, so it is just replacing one problem with another.
Please have a look at this thread:
You can see that dozens of developers have added their experience in hundreds of posts for this specific issue alone, and these are only those developers that actually understand that something is happening, there might be a lot of indies or studios that have not yet noticed that they have a high quota of ANRs in their Air apps that are threatening their visibility on Google Play.
There are at least 2 tickets that reference this bug:
Adobe, please fix this bug as it is affecting all your developers that are using sound, is not easily noticed and is punishing Air developers on Google Play by decreasing visibility for our apps. Please reinforce your commitment to Air by making sure that bugs of this magnitude will be fixed. We are all a little worried since 2 of your engineers have been posting to above thread but have since gone silent after their first attempts of fixing the bug did not work.
Air is a great technology, lets work together to make sure it will stay healthy and efficient. We are ready to step in and help you reproducing the problem. Please let us know if you require more info to reproduce or fix the problem.
Copy link to clipboard
Copied
Please everyone help testing the new SDKs that have been posted yesterday, locally or by uploading to Google Play and reporting results to the thread. I do what I can but I need more testing, and it would be nice to have other reports from other developers as well.
Copy link to clipboard
Copied
What sdk is posted yesterday. It is still the same version from 22 August
Copy link to clipboard
Copied