I’m about to upload a release build to iTunes (which was built with Corona daily build 2419 at 11AM PST), but it looks like Vungle Ads silently fails, so all I see is the backup ads.
Could it be that I must wait for the latest plugin build to propagate and added to build server, then generate my release app before Vungle Ads would work as expected?
Naomi
Hi Naomi,
It sounds like you’re having a different issue. Please email me at tech-support@vungle.com with a code snippet. I’ll want to see the place you init Vungle, play ad, and your build.settings 
Thanks!
Jordyn / Vungle
Will do, Jordyn. Thank you.
Naomi
@Jordyn
Any news on 3.0.10 out of QA?
3.0.10 is out of QA, and we’ve pushed it to our test repo with Corona. This means that it’s likely you’ll have access to it today (or maybe tomorrow). It’s high on my priority list- I’ll be doing the testing in the next hour
Jordyn / Vungle
Update- 3.0.10 is now ready! I’ve just tested and everything looks good. This version should fix the background crash, but if you see any issues, please email me at tech-support@vungle.com
Jordyn / Vungle
Hi Andrew,
I’ve just tested and got no such crash. I use an iPod Touch 4th generation running iOS 6.1.6 and Corona SDK version 2317
I waited 4 minutes and did a suspend and resume with no problem.
After resume I watched a live (non test) Vungle video and then played for over 3 minutes and again suspended and resumed with no crash.
Still, I’m concerned as my customers running on newer hardware with a more recent OS may be experiencing what you are…
Best,
Martin.
Hi Martin, thanks for testing.
My understanding is that the background process limit is 3 minutes on iOS 7 but is 10 minutes on iOS 6 (http://stackoverflow.com/questions/22679845/ios7-background-task-myapp-has-active-assertions-beyond-permitted-time). Since you’re using iOS 6, would you mind trying again but this time waiting 10 minutes instead of 3?
Hi Andrew,
I played my game for 11 minutes and then did a suspend and resume. Still works - no crash on resume.
You could alert Chris Mock at Vungle to this thread. I’ve found Chris to be very helpful in the past.
Best of luck!
Martin.
Hi Martin. Thanks for checking again. My original post may not have been clear. You shouldn’t play the game for 3 (or 10) minutes. Instead, you should launch it, then exit and leave it suspended for 3 (or 10) minutes. The crash occurs *while* the app is suspended. Thus, it’s not horrible from a user experienxe standpoint, but it’s still not good behavior.
Hi Andrew,
This won’t be much use but…
So, I launched the game, exited and restarted just over 10 minutes later. The game started from the very start - not a resume - and there were no errors/crashes/Vungle issues.
Martin.
Hi Andrew and all,
Let me reproduce this on our test iPhone 5 running iOS 7.1.2 and see what we can find. ~Chris
Hi Andrew,
Currently, our iOS Corona plugin is on SDK 308. We have a fix for this issue in 309, which is currently in QA. Should be done pretty soon, then we’ll push it out
Cheers,
Jordyn
Vungle
Tech Support Engineer
Thanks Chris and Jordyn for taking a look and confirming a fix is on the way. If possible, would you mind updating this thread when version 309 is pushed? Unfortunately, Corona doesn’t provide us visibility when plugins are updated (though it’s something I’ve chatted with them about improving), so if you have a chance to post on this thread, that would be fantastic.
We have 3.0.9 available on our dashboard which also means we sent it over to our partners. However, I do not have an exact timeframe when Corona will have it up. Vungle//Chris
Thanks for the update!
Corona team, it would be great if you could reply on this thread when the version 3.0.9 Vungle plugin for iOS that Chris just mentioned is actually up on Corona’s servers.
Hi Andrew,
We pushed 309 yesterday, so if you’re on the newest version of Corona, it should auto-update to 309
Jordyn / Vungle
Thanks Jordyn. I’ve just retested this and I’m still seeing the crash. I retested using the same code as my original post, but this time on Corona 2393 (latest public release) and an iPad 3 running iOS 7.0.4.
Is Vungle 309 set to have a minimum Corona version even higher than Corona 2393 (latest public release)? If so, that would explain why I’m still seeing the crash, in which case I’ll try again with an even newer daily build. If not, then it suggests to me that while you pushed Vungle 309, and hasn’t been integrated into the Corona build process yet for some reason.
Hi Andrew,
So sorry about that! We had a miscommunication over here, but apparently we have not pushed 309 to the public Corona repo, just the one we do testing on. I will update here again when it is ready.
Thanks!
Jordyn/Vungle
My Crash report
Aug 18 14:22:24 Designer-iPad nomsnombers[264] <Warning>: called when add is viewed
Aug 18 14:22:24 Designer-iPad nomsnombers[264] <Warning>: Corona ads ended
Aug 18 14:22:24 Designer-iPad nomsnombers[264] <Warning>: vungleVideoCompleted called
Aug 18 14:22:24 Designer-iPad nomsnombers[264] <Warning>: freeReviveGotAnimation called
Aug 18 14:22:24 Designer-iPad AppStore[265] <Warning>: [SSMetricsEventController] Direct-access controller is calling through XPC to flush Unreported Events
Aug 18 14:22:24 Designer-iPad AppStore[265] <Warning>: [SSMetricsEventController] Direct-access controller is calling through XPC to flush Unreported Events
Aug 18 14:22:26 Designer-iPad ReportCrash[266] <Notice>: ReportCrash acting against PID 264
Aug 18 14:22:26 Designer-iPad ReportCrash[266] <Notice>: Formulating crash report for process nomsnombers[264]
Aug 18 14:22:27 Designer-iPad com.apple.launchd[1] (UIKitApplication:com.funzytime.nomsnombers[0x654e][264]) <Warning>: (UIKitApplication:com.funzytime.nomsnombers[0x654e]) Job appears to have crashed: Segmentation fault: 11
Aug 18 14:22:27 Designer-iPad backboardd[29] <Warning>: Application ‘UIKitApplication:com.funzytime.nomsnombers[0x654e]’ exited abnormally with signal 11: Segmentation fault: 11
Aug 18 14:22:27 Designer-iPad mediaserverd[45] <Warning>: Encountered an XPC error while communicating with backboardd: <error: 0x3a1fa744> { count = 1, contents =
“XPCErrorDescription” => <string: 0x3a1fa9dc> { length = 22, contents = “Connection interrupted” }
}
Aug 18 14:22:27 Designer-iPad ReportCrash[266] <Notice>: Saved crashreport to /var/mobile/Library/Logs/CrashReporter/nomsnombers_2014-08-18-142226_Designer-iPad.plist using uid: 0 gid: 0, synthetic_euid: 501 egid: 0
Aug 18 14:22:27 Designer-iPad mediaserverd[45] <Warning>: 14:22:27.799 [0x23cc000] CMSession retain count > 1!