Vungle ads do not initialise since build 2014.2429 - Error shows up in app

Vungle
#41

@jordyn.chuhaloff, you’re right it works on the public build 2393! Yay :slight_smile:  my error was choosing “None” as “Target App Store” when building with Corona SDK. 

Now I still have a problem, I’m trying incentivized videos and I’m getting two adView (and two adEnd) events after watching a video:

From the terminal:

I/Corona  ( 8877): onSystemEVENT.type:applicationResume

I/Corona  ( 8877): event.type: adEnd

I/Corona  ( 8877): event.type: adView

I/Corona  ( 8877): event.type: adView

I/Corona  ( 8877): event.type: adEnd

 

causing me to reward twice for a single video view. This didn’t happen before with the same code.

#42

@cmontesino:

For the duplicate callback issue, we have a fix in version 3.2.2. The native version is live, and we will be pushing it to Corona this week. There’s already another forum post for this, here: http://forums.coronalabs.com/topic/51378-calling-composergotoscene-in-vungle-callback-throws-error/#entry266474. Please check there, I will update it when we push :slight_smile:

Jordyn /Vungle

#43

Corona don’t maintain the Vungle plugin, Vungle do. Your best course of action would be to report this issue to Vungle directly

#44

I do not think that it is that simple - from previous posts I learned that a certain class is included by Corona in Pro-builds for Vungle to work. Enterprise user have to include this class themselves. If it is missing, Vungle ads won’t work either. Maybe the relevant class has not been included in the recent daily builds for the Pro-users or something else is wrong.

#45

Hi @heftyApps,

I’m Sofie, the Community Manager here at Vungle. Can you please email us at tech-support@vungle.com and we’ll be happy to help figure out the issue. Please feel free to email me directly in the future at sofie.singer@vungle.com.

Thank you for your patience!

Cheers,

Sofie

#46

+1 I have the same error. I am currently using build 2439, the most up-to-date build.

#47

I tried build 2428, but I am not seeing Vungle ads…

I do see this error though:

 

E/GooglePlayServicesUtil( 3019): The Google Play services resources were not found. Check your project configuration to ensure that the resources are included.

 

My build.settings has this, as recommended:

 

        [“CoronaProvider.ads.vungle”] =

        {

            publisherId = “com.vungle”,

        },

        [“plugin.google.play.services”] =

        {

            publisherId = “com.coronalabs”,

        },                

#48

I’m getting the error with build 2014.2438, which fits what everyone else is saying.

#49

I don’t suppose anyone has a guess for why Vungle is failing for me with build 2428?

It’s not that I have never used Vungle – I have it running on an Android game from last year.

EDIT: I am going to try adding a Google Play Games Id to the game…

http://docs.coronalabs.com/daily/plugin/gameNetwork-google/

#50

Hi everyone, 

Corona’s made some changes to Google Ad ID that we will need to incorporate in our plugin. In the meantime, they recommend you include the Facebook plugin, which should cover the missing Google Ad ID. If you have any questions, let me know!

Jordyn / Vungle

#51

I built APK for Google Play using daily build 2419, and Vungle appears to work as expected.  Does this mean there should be no issue with Vungle plugin when built with earlier daily build?  Did the issue start with daily build 2428?

Naomi 

#52

@Naomi: build 2428 works fine for me but the problem start with build 2429 and has not been solved since them. Would be good if someone from Coronalabs could have a look and let us know when/if this will be fixed. I filed a bug Report nearly two weeks ago.

Jens

#53

@Sofie: I sent you an email.

#54

@heftyApps, thank you so much for the details.  I’ll keep it in mind when I need to use more recent daily build for release build my app.

Naomi

#55

I can confirm that including the FB plugin in build.settings makes Vungle work with newer daily builds.

Thanks for the quick assist Jans!

#56

@jflowers45, thanks for confirming the FB plugin settings work. It seems there is still confusion here, so I’ll try to clear it up.

In the most recent Corona daily build, Google Play Services was removed. We now need to add it to our Vungle plugin. The FB plugin has it already, which is why including them in your build.settings will work for now. I’ll update this thread when we’ve added Google Play.

Thanks!

Vungle / Jordyn

#57

Great, thanks everyone for the feedback - looking forward to having this fixed!

Jens

#58

@Jordyn, any news on progress?

Thanks, Jens

#59

When will this be fix? I am going to disable vungle in my app untill a solution come around because it crashes my app <build 23/>

#60

Hey guys I have good news I found a fix for build 23 and up. You just need to include the Google services plugin to your app build settings like this

[“plugin.google.play.services”] =
{
publisherId = “com.coronalabs”
}

Hope this helps,
Ps my app is working find now with vungle

Sean