Ah, good to know. Thank you, Andrew, for verifying this. So it sounds like it’s iOS specific issue. Let’s hope it gets fixed right away.
Naomi
Actually, I spoke too soon. I can get the crash to occur in build 1190 too, and also in build 1179. The reason I at first didn’t reproduce it in 1190 is because I waited for the ad to finish, closed it, and then suspended and resumed. When doing it this way, I can’t reproduce the crash consistently. But now I’m testing by suspending during the Vungle ad, which does seem to reproduce the crash consistently.
- Andrew
Thank you for following up, Andrew. I tested both ways on Android device, and it didn’t crash. So it’s definitely iOS specific issue. Too bad, so plugin update will affect all versions of Corona then…
Naomi
I’m not sure that a plugin update will affect all previous Corona builds though. Even though I’m now able to reproduce this crash going back to build 1179, it’s possible that it already existed then, and we just never noticed it until now. We’ll need to get clarification on how it works from the Corona team in the other thread.
- Andrew
Yeah, I just tested on build 1185 and it still exhibited the crash. I was also able to crash the Vungle Sample app on the Xcode simulator with the older version of Corona. Here’s the link to the sample app:
https://github.com/Vungle/coronaplugin-release/tree/master/samples
To see the crash simply build the sample for the Xcode simulator. Open the app and let it load and play an ad. Once the ad is finished (When I tested it with various builds of Corona it didn’t matter if the ad finished or not, it would still crash) , suspend the app by hitting the virtual home key. Then reopen the app. Within about 5 seconds the app will crash.
My assumption is the plugins are not associated with a particular version of Corona and we always get the latest plugin when we fire up any version of Corona, but it would be good to get some official confirmation from someone at CL to know how it actually works.
Also, this could very well be Corona Labs’ bug. The plugin might have worked against some previous build that Vungle used to create the plugin but there could have been a regression bug in a later version of Corona that broke the plugin. Still, without transparency or communication (hello Corona Labs? Mr. Vungle?) we’re in the dark.
Also, just to confirm Naomi’s findings, I couldn’t get the same crash on an Android device so so far it looks like an iOS specific issue.
Well, so far 3 days and several emails to tech-support@vungle.com and I have yet to get a response. Not exactly building up my confidence in the viability of this “featured partner” of Corona. It’s too bad because the video interstitials seemed to be of high quality. I guess I’ll have to rip Vungle out and use a different ad provider :unsure:
And… cue the response from tech support:
Apologies for the delay in response – we’ve actually had a number of
these problems come through in the last few days. It stems from a recent
change we made to the underlying iOS SDK in order to ensure
compatibility with iOS 7, and it seems to have broken the Corona plugin
for a number of publishers.We’re planning on rolling out an update by the end of the week.
Whew!
Thanks for the update, Stephen @HardBoiledIndustries. Glad to hear it is being addressed.
Naomi
I see that there was an update to Vungle Plugin a day ago:
https://github.com/Vungle/coronaplugin-release
I wonder if it is deployed already, and whether or not it fixed the issue with iOS version.
FYI, I am just about ready to upload an update to Google Play, and so far, I haven’t seen any issue with Vungle on Android device – and I’ve done tons and tons of testing. In fact, I’m just about ready to to feel sick doing this whole back key & home key, and various combination thereof while video is playing as well as after the video ends.
In other words, the latest vungle plugin update probably didn’t affect Android version (which is a good thing.)
Naomi
@Naomi, this is probably I stupid question, but do we need to do anything to “update” Vungle? I will assume not since it is a plugin and so the update is done for us?
I still need to check if the issue raised by hardboiledegg has been resolved since I am preparing a new update with all the ad networks implemented (Vungle,Chartboost and Revmob)
Thanks a lot.
Mo
@Mo, from what I understand, the plugin updates happen behind the scene, and they’re not tied to any specific Corona Builds. So, when you generate a new device build, if you require a plugin, its latest version would be incorporated into the device build. At least that’s what I understand to be the case.
Naomi
Thanks Naomi. I am not clear on this. So if an app is already in the store, it will need to be updated then? I hope not but it will be great to know.
Cheers.
Mo
Hey Mo, you’ll need to update and generate a new release build with the updated plugin, submit it to Apple and get it to store before your users can have this fix.
Naomi
Ok, that makes a lot of sense. Thanks for your patience Naomi 
Take care.
Mo
I just rebuilt my app using Corona build 1203 and (presumably) the updated version of the Vungle plugin and it still crashed on my iOS device after a suspend/resume, so, unfortunately, it doesn’t look like the update addressed the problem. I haven’t had any problems with Vungle on Android devices.
Thank you for checking, Stephen @HBI. Sorry to hear that the latest update didn’t fix the issue.
Naomi
Hey, Stephen @HBI, I’m sure you’ve heard from Vungle that they’ve released the updated version to work with iOS7. Upon further inquiry, I’ve heard back that they submitted the updated plugin about an hour ago. Let’s hope this update will take care of this crash bug.
Naomi
Thanks Naomi, they did let me know they were working on pushing a fix through today/tomorrow. I requested they post to the Corona forum when the new version is available.
Good news, just tested on my iPhone 5 and Vungle no longer crashes my app, so the updated plugin must be live. Not sure if it matters but I used the latest Corona build 1206.