Hi,
I have the Corona public release build 2189 and am building my app for iOS but calling ads.init() with vungle freezes my app. The function call never returns and thus code execution stops in its tracks. The logs on the device are silent as well.
Is there any info about why the iOS vungle plugin is not working? It was working a couple weeks ago but now it doesn’t work.
Hi @spacewolf,
I believe Vungle is updating some things within the plugin. Please do a forum search and see what turns up within the past few weeks.
Brent
Hello Spacewolf,
Sorry to hear you are encountering some issues with the latest build. We have a ticket open with you currently and waiting for the code. Once we can review we’ll be sure to let you know what we find.
I am working with @chris via email…
In the mean time, is anyone else experiencing vungle plugin issues when building for iOS, or am I the only one? Curious to see if it is an isolated issue or more widespread. Please sound off! 
@spacewolf, FYI, Vungle ads show up without any problem with the iOS version built with Daily Build 2370 for me.
Naomi
@Naomi, thanks for chiming in. Good to see it is working on the daily build.
For those of us still on the last public release 2189, anyone having an issue?
I was having an issue with Vungle, but not anymore with their latest plugin version.
One thing to note is that my project is an Enterprise project, which means I use Xcode to compile locally. I saw that Vungle had updated their plugin, and after linking in their new plugin version the issues were gone.
BTW.
I’m surprised that you say your app was working and then all-of-sudden it stopped working. To me that sounds like maybe you’re getting the latest Vungle plugin linked in although you’re using the public version (and that the plugin requires a later daily build).
I was under the impression that plugins were linked based on the build that was used. Maybe I’m wrong. However if you *are* getting a plugin that requires a later Corona build, there might be some bug with CoronaLabs “plugin chooser” which is giving you a version of a plugin that you shouldn’t get. Just a thought.
I noticed that the version of IOS you are using vungle on plays a factor. On ios 5.1.1 I see the same issue with vungle initialization never returning but newer versions of IOS work fine.
I was testing on an iPhone 4 and it had an old version of iOS running on it. I’m not sure which but I have a feeling it was 5. I updated my device to the latest version (7.1) and the vungle code is working again.
So it sounds like the vungle init doesn’t return if running on an older version of iOS.
Vungle guys, looks like you got a bug here!
I guess it’s easily overlooked as Corona doesn’t support iOS 5 as of build 2277 (released in April 2014)
Thanks for the details of the version of iOS. Issues iOS 5 related will be addressed in the 3.0.9 Vungle SDK, which is currently in testing.
Hi @spacewolf,
I believe Vungle is updating some things within the plugin. Please do a forum search and see what turns up within the past few weeks.
Brent
Hello Spacewolf,
Sorry to hear you are encountering some issues with the latest build. We have a ticket open with you currently and waiting for the code. Once we can review we’ll be sure to let you know what we find.
I am working with @chris via email…
In the mean time, is anyone else experiencing vungle plugin issues when building for iOS, or am I the only one? Curious to see if it is an isolated issue or more widespread. Please sound off!
@spacewolf, FYI, Vungle ads show up without any problem with the iOS version built with Daily Build 2370 for me.
Naomi
@Naomi, thanks for chiming in. Good to see it is working on the daily build.
For those of us still on the last public release 2189, anyone having an issue?
I was having an issue with Vungle, but not anymore with their latest plugin version.
One thing to note is that my project is an Enterprise project, which means I use Xcode to compile locally. I saw that Vungle had updated their plugin, and after linking in their new plugin version the issues were gone.
BTW.
I’m surprised that you say your app was working and then all-of-sudden it stopped working. To me that sounds like maybe you’re getting the latest Vungle plugin linked in although you’re using the public version (and that the plugin requires a later daily build).
I was under the impression that plugins were linked based on the build that was used. Maybe I’m wrong. However if you *are* getting a plugin that requires a later Corona build, there might be some bug with CoronaLabs “plugin chooser” which is giving you a version of a plugin that you shouldn’t get. Just a thought.
I noticed that the version of IOS you are using vungle on plays a factor. On ios 5.1.1 I see the same issue with vungle initialization never returning but newer versions of IOS work fine.
I was testing on an iPhone 4 and it had an old version of iOS running on it. I’m not sure which but I have a feeling it was 5. I updated my device to the latest version (7.1) and the vungle code is working again.
So it sounds like the vungle init doesn’t return if running on an older version of iOS.
Vungle guys, looks like you got a bug here!
I guess it’s easily overlooked as Corona doesn’t support iOS 5 as of build 2277 (released in April 2014)