@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.
Thanks for the update. I just tried with Daily Build 1203, and it’s not crashing there either. This suggests that the new version of the plugin was applied retroactively to previous builds (since earlier, you’d noted that it was crashing on 1203), which is a pretty worrisome thing!
Andrew,
Yes, I think the way it works is, no matter what build you are using, it pulls the latest plugin from the host server during that little pre-build pause when you build for the simulator.
I agree it’s asking for lots of confusion and potential mayhem when we don’t have any transparency into the plugin development or communication with the developers who make them. For example, the Vungle support guy was very nice via email, and they were pretty timely with their update, but even though I requested they post here when they updated the plugin they didn’t. So how would Corona users normally know that a plugin was updated, if only to test it in their own apps to make sure it doesn’t introduce a new bug? And if it does have a new problem how can we roll back to a previous version of the plugin? (A: We can’t!)
I would really like to hear what Corona Labs has to say about this issue that you raised here and in your other thread, but I’m afraid it’s a messy problem without an obvious solution.
Yeah, I agree we need to hear from Corona staff about it. At a minimum, publishing a changelog for third-party plugins would at least alert us to the fact that a plugin has been updated. Without that, we’re completely in the dark.
I just tested the Vungle sample app on the Xcode simulator and is also crashes if I do a suspend/resume after the ad plays. So it is a bug unrelated to my code and will likely crash any Corona app using the Vungle plugin to display ads.
Since this is a third party plugin what is the process for getting this bug the attention it needs?
Hey, @HardBoiledIndustries, try sending email to tech-support@vungle.com with details and mention Corona SDK plugin. Based on my experience, they are very responsive.
Naomi
Thanks Naomi, I did manage to find that tech support email on their site (I think the link to it from Corona’s docs is incorrect). Hopefully I’ll hear back from them soon.
I’m curious if you are using Vungle in any of your apps, live or not, and if you’re able to reproduce the crash I describe. Since I was able to crash their sample app I’m afraid it could be a problem that affects anyone using the current Vungle plugin. Would love to be proved wrong.
-Stephen
Hi Stephen,
Thanks for highlighting this. I’ve just experienced this issue in daily build 1202, iPhone 5 running iOS 6.1.
I don’t remember having an issue like this a few weeks ago, so I suspect that Vungle updated their plugin behind-the-scenes, introducing this bug. It points to the importance of getting changelogs for the plugins, which currently we don’t get.
Hi Andrew,
Thanks for the confirmation. I got an auto response from Vungle that they received my email to support so fingers crossed they will respond and push out a fix soon.
It’s not exactly a change log but I found the github where they are hosting the plugin code. It indicates the last update occurred 5 days ago (to fix an Android issue that seems unrelated to this bug).
https://github.com/Vungle/coronaplugin-release
I agree we need more transparency wrt plugin updates. As we rely more and more on third party plugins it could get messy not knowing if a plugin has been updated and potentially introducing a new bug, especially if the third party doesn’t have a presence on these forums. And we can’t roll back to a previous version if a problem is discovered.
Hi Stephen,
Glad we’re in agreement about the need for more transparency when third-party plugins change. I started a thread about it here: http://forums.coronalabs.com/topic/39238-plugin-changelogs-and-regression-bugs/.
I agree with both of you, Stephen @HardBoiledIndustries and Andrew @aukStudios.
BTW, the issue you posted, Stephen, is not present on Android device. I’ll let you know how it goes on my end once I had a chance to test this issue on iOS device.
Let’s hope you’ll hear back from Vungle tech person soon.
Naomi
FYI, I just tried rebuilding my app using daily build 1190, and the crash didn’t occur, whereas it does occur in build 1202. This suggests that plugin versions are indeed tied to daily build versions, which answers one of the questions I raised in the other thread: http://forums.coronalabs.com/topic/39238-plugin-changelogs-and-regression-bugs/.