New test build is up - if you have ability to test it that would be amazing: Daily Build · coronalabs/corona@791c8b0 · GitHub
Building with this test, and any call to purchase via IAP cause the app to close
Thanks a lot. Looking into it
Thanks Vlad, doesn’t close anymore on IAP! Just submitted to Google, will let you know results in a few days.
@vlads Early results are good from us. 800 sessions, and no ANRs. In all previous builds we’d have seen 3-4 ANRs so far with that number of sessions.
So, 3700 is out, having this changes upstream:
Thanks Vlad!
Just to echo what @kbradford said, our ANR rate also went down dramatically using the new build.
We’ve gone underneath the bad behaviour threshold for the first time ever.
@anon63346430 I know you’ve had similar ANR issues for a long time too, so if you’re still monitoring this thread I 100% recommend updating to the latest build.
Cool, my next update is due in a few weeks so, assuming nothing breaks, I’ll try this. Got any graphs on the ANR drop @alanFlickGames ?
Sure. This is the “all versions” graph. Update made with the new build was started on the 24th.
And this is the rate for the new version by itself:
It looks like our peers also struggle to stay below the rate, so being consistently below them for the last 4 days is a positive sign.
Good news so far… I wonder if this affects ranking?
ANRs are down, how about the crashes though?
All my games share the same plugins and ad networks but only in this one I get ANRs and crashes over the threshold!
OMG do you any organics with that crash rate? What are the crashes reported in console?
This game gets 150 - 450 downloads daily (100k+ total downloads).
It’s the first time any of my games has anr or crash rate over the threshold.
In Android vitals → Crashes and ANRs these are the user-perceived crashes of version in production.
November 9 - December 7
Shouldn’t it show much more crashes? It’s really the first time I check these things!
Am I looking at the wrong place maybe?
Also I got this in Android vitals → Overview
Does it mean that latest version 121 (in production, published previous week) has less crashes?
Here is my build.settings too if it helps track the crashes!
settings =
{
splashScreen =
{
enable = false
},
orientation =
{
default = "landscape",
supported =
{
"landscapeRight", "landscapeLeft"
},
},
android =
{
versionCode = "121",
applicationChildElements =
{
[[
<meta-data android:name="com.google.android.gms.ads.APPLICATION_ID"
android:value="ca-app-pub-xxx~xxx"/>
]],
},
manifestChildElements = { [[
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" tools:node="remove" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" tools:node="remove" /> ]],
},
minSdkVersion = "16",
usesPermissions =
{
"android.permission.INTERNET",
"android.permission.ACCESS_WIFI_STATE",
"android.permission.READ_PHONE_STATE",
"android.permission.ACCESS_NETWORK_STATE",
"android.permission.WRITE_EXTERNAL_STORAGE"
},
},
plugins =
{
-- normal
['plugin.appodeal.beta.base'] = { publisherId = 'com.coronalabs' },
['plugin.appodeal.beta.GoogleAdMob'] = { publisherId = 'com.coronalabs' },
['plugin.appodeal.beta.AdColony'] = { publisherId = 'com.coronalabs' },
["plugin.utf8"] =
{
publisherId = "com.coronalabs"
},
["plugin.openssl"] =
{
publisherId = "com.coronalabs"
},
},
}
Does it mean that latest version 121 (in production, published previous week) has less crashes?
That image from Overview shows 121 as being 10.50%, so basically the same rate as the other versions.
That is a very high rate - for comparison our crash rate is about 0.16% and has been around that rate for years.
I’m not sure why the first image only shows you 2 crashes though, unless it’s being filtered somewhere outside the image.
The utf8 and openssl plugins should both be pretty stable, they’ve been around for a long time.
I don’t think there’s anything inherently broken in the Solar2D SDK itself that would cause a crash rate this high, or we’d all be experiencing it.
If I had to guess why the rate is so high, you’ve either got an error in your code or there’s an error in the Appodeal plugin/SDK. I don’t know how many others use Appodeal, but I assume some devs here use it so if the problem was there I think we would have more reports of it.
All of my games have low crash rate except this one.
And all started from build 3692.
No filtering.
If it wasn’t this game I would be one of the developers that have no problem.
Also my other games had not even anr rise but it didn’t mean that there was no problem with solar2d.
This definitely seems extremely high. I wonder why it’s not showing you the crashes when you try to view them.
Check the filter for “type” and make sure it’s set to “All crashes”. Maybe that would help.
Something is clearly going wrong in the console then, because the Breakdown section showed you had ~525 crashes in version 121 but that last image is only showing 3 in that version.