@ran5: any updates? Still waiting for the updates…
According to Kidoz, their update was ready November 7th. Waiting for Corona to publish, expected early next week.
I’ve voiced my frustration at the delay to Kidoz.
Hi all,
Thanks for waiting.
Just a quick update, the new sdk version was published: https://forums.coronalabs.com/topic/67433-kidoz-plugin-update/#entry371445
As always, in case of any questions please reach out and contact us at sdk@kidoz.net.
Hi @ran5 i updated our app on 3 December and still getting a very High number of ANR’s (1.7%) on the latest uploaded apk.
executing service com.mypackagename/shared.google.play.services.base.PackageStateChangedService
is still the culprit for the majority of the ANRs
https://forums.coronalabs.com/topic/67433-kidoz-plugin-update/#entry371445 says it was updated 29th november so i should have the latest update of kidoz and used the latest dailybuild.
On another note, it mentions in the above link that banners now dont have to be reloaded, but once i hide the banner, it wont show anymore unless i reload it. also getting quite alot of banner loaded=failed today aswell
@chris_raz This issue has been plaguing me for a month or more. I have been through 8 different rollouts of my app, with various configurations enabling/disabling Admob, Kidoz and Firebase. I’ve been extracting and comparing the manifests using https://github.com/ytsutano/axmldec, and checking ANRs and crashes in Google Play.
At this point, I have reached the fuzzy conclusion that something doesn’t play nice when the three plugins mentioned above are used together - at least in my setup (YMMV).
Firebase on its own has worked well in my Balloon Pop app, no issues.
Kidoz on its own works well now.
Kidoz and Admob seems work ok now, although more ANRs than just Kidoz.
Adding Firebase seems to trips things up.
So I’m removing Firebase, and removing Admob unless I use it in a particular app. Some apps will have just Kidoz, some will have Kidoz and Admob.
Thanks for the detailed responce @plerflubron … just uploaded an update to one of our apps, removed admob, dont have firebase, just kidoz now, so will see if that helps. Will post an update once the numbers start coming in
Any new insight on this? The same error is the top one in our ANR list:
executing service
io.torcia.idletraveler/shared.google.play.services.base.PackageStateChangedService
shared.google.play.services.base.PackageStateChangedService
Our ANR rate is about 0.78% and this error makes about 60% of all ANR reports.
We are using Scott Harrisons’s Firebase plugin for analytics and AppLovin for video ads. So first thought was, that the AppLovin plugin does also have problems.
On the other hand I know that this Firebase plugin does not work well together with Corona’s Firebase push notifications like I stated in this post (which is why we do not use any push notifications right now).
I am just want to state this one more time. Unless you see an error inside LuaLoader or something that has to do with my Plugin like “plugin.firebaseAnalytics” it is probably not this fault. shared. means that corona hosts this library. While this may not be their fault ( could be a google bug), only they can change or edit. I already stated firebase notification problem in the link shared above, but it is not relevant to this issue.
This ANR is hitting hard, it serious as it affects the bottom line as you said.
10k users affected !
How did you came to conclusion it’s related to plugins? I see libopenal.so in the trace
I am in the same boat as many people here. I am down to .68% for ANRs but that is still above the bad behavior threshold. I am running out of plugins to remove.
Has anybody figured this out yet?
Same problem 
Using admob plugin
Our engineers are investigating the source of these sudden increase in ANR’s and crashes.
Any update on this? Same here, ANRs have gone up.
ANR’s and crashes are coming from different causes and it’s weird that apps that didn’t get any updates are now ANRing and crashing which tells me that Google has made some updates in Android that’s now causing these issue.
Anyway, we are addressing them. Android audio with OpenAL is one big source of problems and we are testing out a replacement system and will hopefully get that out soon. The other source seems to be plugins that depend on some of the Google Play dependencies. We are in the process of updating a bunch of plugins to use the latest Google dependency libraries. As those plugins get updated, builds will get the updates.
So stay tuned. We hope to have more information soon.
Rob
Thank you for the update Rob! Looking forward to it!
Hey guys. Liking through all of the crash logs there are no reference to PackageStateChangedService in crash logs you posted. They all leading to OpenAL library… Honestly, I have no idea why google decides PackageStateChangedService is at fault. Please, make sure to pus FULL output of the ANRs page, not just first parts.