Did you try the 2162? With this version the game doesn’t crash for me.
2162? From back in February? That would be way too old for us, there have been other fixes we rely on since then.
I just tried building my app with vungle for iOS on the current corona public release and it does NOT work. The call to ads.init() never returns. The app doesn’t crash it just sits there. No messages in the log about it either… just nothing!
Please help!
Is anyone else having problems still??
I got a hold of the team. The requirement is based around needing to use the Google Play app. I’m guessing this is due to the changes Google is enforcing over their new advertising identifier requirements. This requires apps be built with a minimum Android SDK of 2.3.3. This is the change we made in daily build 2264 (If my memory serves me correctly). This is the same requirements that the AdMob V2 plugin has.
Until we release a new public build, the new Vungle plugin will only be available to Pro and Enterprise subscribers running 2264 or later. It sounds like from reading this thread, pre-2264 will get an older version of the Vungle plugin, which won’t be compliant with Google’s requirements after August 1st.
If you are building with Enterprise, you probably need to change your minimum SDK to 2.3.3 and grab the latest plugins.zip file since you don’t automatically get new plugins when they come out.
As for the issues with it crashing with later daily builds, hopefully Vungle can get that sorted out for you.
I have the public release build 2189 and am building my app for iOS but it freezes my app when I call ads.init() for vungle. Is there any info about why the iOS plugin of vungle is not working? It was working a couple weeks ago…
Can Sofie or someone else from Vungle give us an eta on when they expect this plugin to be fixed?
A few days ago you said a fix had been pushed through to Corona, but it seems that it has not worked.
Still doesn’t work on latest daily build 2373, same error.
Please fix this problem, it’s a blocker and we cannot release an update for our app!
Can someone from Vungle please let us know what is going on? We really need to publish an update on Android ASAP and with no Vungle plugin we could be losing a good source of our revenue.
It’s starting to feel like the silence is indicative of “we have no idea what’s happening”. The last we heard was that a fix had been pushed last Thursday, but there seems to be no evidence of that.
Hi everyone,
So sorry about this issue – those of you with the daily build should have been able to update. Your code should match this:
For everyone else – if you do not have the daily build, you need to remove the google services from the plugin section of your build.settings.
Please feel free to email me at sofie.singer@vungle.com or our tech support team directly at tech-support@vungle.com directly with any further questions.
Thank you all for your patience!
Cheers,
Sofie
Hello Sofie,
Thank you!
I can confirm that app doesn’t crash with daily build 2374, but build.settings file has to be modified:
["CoronaProvider.ads.vungle"] = { publisherId = "com.vungle", }, -- Add Google Play Services ["plugin.google.play.services"] = { publisherId = "com.coronalabs" },
If Google Play Services plugin is not there, then app will still crash.
Sofie, can you elaborate on why do we need to add this additional dependency?
I can confirm that the plugin is working for me on Android now.
The reason it didn’t work when I updated my daily build is because nobody thought it necessary to tell us we needed to add the google play plugin to build.settings.
Hi there,
Apologies for any confusion – we will be updating our documentation very soon.
Thanks for your patience!
Cheers,
Sofie
The same case with me . :wacko:
Good to know I’m not alone.
Took me a while to figure out what caused this…
Looks like it’s something to do with the ad indentifier, at least on Android:
07-16 10:07:29.842: E/VungleAsync(13366): java.lang.NoClassDefFoundError: com.google.android.gms.ads.identifier.AdvertisingIdClient 07-16 10:07:29.842: E/VungleAsync(13366): at com.vungle.publisher.env.AdvertisingDeviceIdStrategy$FetchAdvertisingPreferencesRunnable.run(vungle:45) 07-16 10:07:29.842: E/VungleAsync(13366): at com.vungle.publisher.async.ScheduledPriorityExecutor$a$a.run(vungle:234) 07-16 10:07:29.842: E/VungleAsync(13366): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112) 07-16 10:07:29.842: E/VungleAsync(13366): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587) 07-16 10:07:29.842: E/VungleAsync(13366): at java.lang.Thread.run(Thread.java:841) 07-16 10:07:29.842: W/dalvikvm(13366): threadid=16: thread exiting with uncaught exception (group=0x41882da0) 07-16 10:07:29.842: E/VungleAsync(13366): java.lang.NoClassDefFoundError: com.google.android.gms.ads.identifier.AdvertisingIdClient 07-16 10:07:29.842: E/VungleAsync(13366): at com.vungle.publisher.env.AdvertisingDeviceIdStrategy$FetchAdvertisingPreferencesRunnable.run(vungle:45) 07-16 10:07:29.842: E/VungleAsync(13366): at com.vungle.publisher.async.ScheduledPriorityExecutor$a$a.run(vungle:234) 07-16 10:07:29.842: E/VungleAsync(13366): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112) 07-16 10:07:29.842: E/VungleAsync(13366): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587) 07-16 10:07:29.842: E/VungleAsync(13366): at java.lang.Thread.run(Thread.java:841) 07-16 10:07:29.842: W/dalvikvm(13366): threadid=17: thread exiting with uncaught exception (group=0x41882da0) 07-16 10:07:29.842: I/Process(13366): Sending signal. PID: 13366 SIG: 9 07-16 10:07:29.842: E/AndroidRuntime(13366): FATAL EXCEPTION: VungleAsyncMainThread-0 07-16 10:07:29.842: E/AndroidRuntime(13366): Process: com.mycompany.mygame, PID: 13366 07-16 10:07:29.842: E/AndroidRuntime(13366): java.lang.NoClassDefFoundError: com.google.android.gms.ads.identifier.AdvertisingIdClient 07-16 10:07:29.842: E/AndroidRuntime(13366): at com.vungle.publisher.env.AdvertisingDeviceIdStrategy$FetchAdvertisingPreferencesRunnable.run(vungle:45) 07-16 10:07:29.842: E/AndroidRuntime(13366): at com.vungle.publisher.async.ScheduledPriorityExecutor$a$a.run(vungle:234) 07-16 10:07:29.842: E/AndroidRuntime(13366): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112) 07-16 10:07:29.842: E/AndroidRuntime(13366): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587) 07-16 10:07:29.842: E/AndroidRuntime(13366): at java.lang.Thread.run(Thread.java:841) 07-16 10:07:29.862: I/ActivityManager(813): Process com.mycompany.mygame (pid 13366) (adj 0) has died. 07-16 10:07:29.862: I/WindowState(813): WIN DEATH: Window{430da980 u0 com.mycompany.mygame/com.ansca.corona.CoronaActivity} 07-16 10:07:29.862: I/SurfaceFlinger(277): id=702 Removed TurfaceView (17/20) 07-16 10:07:29.862: I/SurfaceFlinger(277): id=702 Removed TurfaceView (-2/20) 07-16 10:07:29.862: D/KeyguardViewMediator(1233): setHidden false 07-16 10:07:29.862: D/KeyguardUpdateMonitor(1233): sendKeyguardVisibilityChanged(true) 07-16 10:07:29.862: D/KeyguardUpdateMonitor(1233): handleKeyguardVisibilityChanged(1) 07-16 10:07:29.862: W/WindowManager(813): Force-removing child win Window{43a8fb00 u0 SurfaceView} from container Window{430da980 u0 com.mycompany.mygame/com.ansca.corona.CoronaActivity} 07-16 10:07:29.862: W/ContextImpl(813): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1479 com.android.server.am.ActivityStack.removeHistoryRecordsForAppLocked:3697 com.android.server.am.ActivityStack.handleAppDiedLocked:4461 com.android.server.am.ActivityStackSupervisor.handleAppDiedLocked:2965 com.android.server.am.ActivityManagerService.handleAppDiedLocked:4562 07-16 10:07:29.862: W/ActivityManager(813): Force removing ActivityRecord{42e48ac8 u0 com.mycompany.mygame/com.ansca.corona.CoronaActivity t47}: app died, no saved state
Can someone from Corona let us know if they have any ideas on this please? We were planning on submitting today.
Can confirm that it doesn’t happen on iOS for me, how about everyone else?
Same for me :S
Same here. Already released apps are working fine. Can only speak of Android right now.
Hi @Paskuniak,
I’m the Community Manager here at Vungle. Thank you so much for reporting this! Our team is working to fix the issue ASAP. Thank you for your patience and please feel free to email me directly at sofie.singer@vungle.com with any questions. We’ll update you as soon as the issue is resolved.
Cheers,
Sofie