Is there a way to follow the bug report/ticket or will you update us here when there is a fix?
In general if the person filing the bug report includes a link to the forum post, we can come back and update the forum post. If not, you have to watch the change log. The bug reporter will get an email, with follow up questions as necessary and updates as we process the bug.
I don’t know if @sgs included the forum link in the submission form or not.
Rob
UPDATE: Vungle are going to be patching the SDK.
They have said “there will be an iOS release and corona plugin will be released with the fix for this android issue as well on 12th of March.”
Hopefully, this will address the crashes and the duplication of events being raised by the SDK. If not then it points to a framework issue as I doubt Google have done any updates to Android 6 recently.
@Rob, if they do patch the plugin March 12th, how long til it is available for sim builds?
Thanks
Once they upload the plugin to our servers, it will be live in about an hour.
Rob
Hey Rob, can you see if Vungle have patched today?
It does not appear that Vungle has updated today, but it’s still early.
Rob
Seems the Vungle patch fixed the multiple events bug but NOT the crashes on Android 6.
The stack trace for the crashes is
java.lang.NullPointerException: Attempt to invoke virtual method 'void android.app.Activity.runOnUiThread(java.lang.Runnable)' on a null object reference Java Stack Trace: plugin.vungle.LuaLoader.init(LuaLoader.java:176) plugin.vungle.LuaLoader$InitWrapper.invoke(LuaLoader.java:132) com.ansca.corona.JavaToNativeShim.nativeRender(Native Method) com.ansca.corona.JavaToNativeShim.render(JavaToNativeShim.java:182) com.ansca.corona.Controller.updateRuntimeState(Controller.java:347) com.ansca.corona.graphics.opengl.CoronaGLSurfaceView$CoronaRenderer.onDrawFrame(CoronaGLSurfaceView.java:425) com.ansca.corona.graphics.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1623) com.ansca.corona.graphics.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1378) stack traceback: [C]: in function 'init' ?: in function 'vungle\_Init' ?: in function 'method' /Users/jenkins/slaveroot/workspace/Templates/label/android/platform/resources/init.lua:221: in function 'dispatchEvent' ?: in function 'gotoScene' ?: in function 'listener' /Users/jenkins/slaveroot/workspace/Templates/label/android/subrepos/timer/timer.lua:210: in function 'method' /Users/jenkins/slaveroot/workspace/Templates/label/android/platform/resources/init.lua:221: in function \</Users/jenkins/slaveroot/workspace/Templates/label/android/platform/resources/init.lua:190\>We have asked Vungle to look into this.
Rob
Hi, any updates from Vungle or other developments on this?
I was hoping we’d have fixes faster than this. We’re hurting with these ANRs and crashes.
Vungle was updated on 3/14. I don’t know what was addressed. Our engineers are rolling out updated plugins every day or so that should address many of these crashes. The problem is there are many things we have to do to have them all, but nothing says you can’t build now and pick up the things that are already fixed to start seeing if there are improvements. But if you do update today, you won’t get them all, but you can start knocking them down if the fixed plugins are in the set you are using. We probably won’t make an announcement until they are all done.
If you are experiencing OpenAL errors, you can go ahead and test your app against the Beta of the new Android Audio API’s (call compatible with audio.*) and if you’re happy with the performance and don’t find bugs, you could attempt to release with that and see if it starts knocking down your Open AL errors (note it will take time for your game to update to everyone). However, we may have errors in the new audio api’s that will create ANRs and Crashes. But we will need to know about those to fix them.
Rob
Are you sure @Rob? I got an email from Vungle (Apr 4, 11:30 AM PDT) informing me they have updated the plugin to address the Android 6 crashes.
Can you confirm if they checked anything in since Mar 14th?
I don’t see any changes to the repository since March 14.
I’m not too involved with 3rd party plugins any more, so I can only look at the server and see dates.
Rob
Update : Majority of the crashes seem to be on Android 6.0
It could be there are less on 7.0 because we don’t have enough users running that version.
Any more updates from Vungle or with Audio 2.0?
Well after assuring me they had fixed it I released an staged rollout… After 1 day my crash rate was up 50% so I halted the rollout and reverted to SDK 4 and continued the rollout.
Currently, I am 5 crashes on 5k installs - a 77.8% improvement in crash rate and something that is a tangible benefit.
Long story short; Vungle SDK 5 is broken on Android 6 (still some 30% install base) and I’m not prepared to waste any more time (or rankings) trying to get Vungle to sort it out.
Caught a crash in a Pre-launch report:
Looks like a Vungle and audio library conflict???
Vungle engineers probably need to look at this…
04-18 02:08:20.139: D/AudioService(3347): getStreamVolume 3 index 80
04-18 02:08:20.139: D/AudioService(3347): getStreamVolume 3 index 80
04-18 02:08:20.159: E/VungleDevice(16615): error getting available bytes
04-18 02:08:20.179: I/Corona(16615): CheckForAds
04-18 02:08:20.179: I/Corona(16615): CheckForAdsVungle false false
04-18 02:08:20.219: A/google-breakpad(17129): -----BEGIN BREAKPAD MICRODUMP-----
… clipped …
04-18 02:08:20.239: A/google-breakpad(17129): -----END BREAKPAD MICRODUMP-----
04-18 02:08:20.259: W/google-breakpad(16615): ### ### ### ### ### ### ### ### ### ### ### ### ###
04-18 02:08:20.259: W/google-breakpad(16615): Chrome build fingerprint:
04-18 02:08:20.259: W/google-breakpad(16615): 1.63
04-18 02:08:20.259: W/google-breakpad(16615): 250
04-18 02:08:20.259: W/google-breakpad(16615): a62ada37-657b-4454-8f33-6399db62ca12
04-18 02:08:20.259: W/google-breakpad(16615): ### ### ### ### ### ### ### ### ### ### ### ### ###
04-18 02:08:20.259: A/libc(16615): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x8 in tid 16934 (VungleAsyncMain)
04-18 02:08:20.279: D/AudioFlinger(3017): mixer(0xee280000) throttle end: throttle time(1)
04-18 02:08:20.289: V/AlarmManager(3347): remove PendingIntent] PendingIntent{db6b8a7: PendingIntentRecord{651c41a com.google.android.gms broadcastIntent}}
04-18 02:08:20.319: D/PackageManager(3347): setEnabledSetting : userId = 0 packageName = com.google.android.gms cmp = com.google.android.gms.locationsharing.service.LocationSharingSettingInjectorService newState = 1 callingPackage = 10021
04-18 02:08:20.329: I/TestSupport(14418): AwaitCommitOperation: uncommitted: FlagOverride(com.google.android.gms.auth_account, , Flag(auth_sig_override_enabled, true, 2, 0), false)
etc.
Hey guys!
We are trying to get Vungle updated on those issues, no worries. We’ll provide them any help needed to insure that plugin will be updated asap. Can’t say anything more on the subject, tho. <_<
So lets examine this a bit… so I moved from vungle SDK 4 to SDK 5 and have noticed a massive increase in crashes. I will represent this with a graphic.
The only thing I added with this release was Vungle SDK 5 to monetize Amazon players (this was unsupported in SDK 4).
Now bear in mind some 15k DAU then 50 crashes might seem acceptable (low mem, etc) but a 4x increase certainly is not. Do note this is entirely limited to Android 6 so therefore is a framework/plugin issue.
Now I am sure Corona will say “oh Vungle maintain their own plugin” and whilst I get that, you are surfacing that as a Corona plugin so surely there is some ownership there? After all Amazon take ownership of all their sellers, etc.
Please also note this recent post which is related https://forums.coronalabs.com/topic/71859-crash-report-signal-11-sigsegv-code-1-segv-maperr-zn3art11interpreter6docallilb0elb1eeebpns-9artmethodepns-6threaderns-11shadowframeepkns-11i/
So perhaps there can be some investigation?
Hi, I wanted to add that in addition to seeing the crash report above, I’ve seen other issues with the latest Vungle plugin. One that I reported directly to Vungle a couple weeks ago.
Issue 1:
One of the ads will keep playing a music loop after it is dismissed. What’s worse is it keeps playing even when leaving the app unless you completely close the app. I’ve only seen this on iOS so far but it may happen on Android as well.
Issue 2:
On Amazon when clicking on some ads it will take you to a browser and then bring up a completely different app than what is being advertised. I realize Vungle is new on Amazon and inventory is low, but this needs to be reported. If you need more detail, I will ask a tester to send it to me or try to re-produce the problem myself.
I’m not clear about your release schedule. Is the change to 3200 timed with the increase in crashes, or have you been using 3200 for previous releases and the change to Vungle 5 is reflected by this change?
I’ll be happy to email our contact at Vungle and have them look into this. As you mentioned, we have no access to their source code. They are pretty good about watching their specific forum for issues, but with this being in a general content forum, I’ll make sure they are aware of this thread.
Rob