Is it OK to keep using ["CoronaProvider.ads.vungle"]?

Solar2D Monetization (in-app purchases, ads, etc.)
#1

My build.settings:

 ["CoronaProvider.ads.vungle"] = { publisherId = "com.vungle", },

Notice that there is no  [“plugin.google.play.services”]

How I display ads:

local ads = require( "ads" ) ads:setCurrentProvider( "vungle" ) ads.show( "interstitial", { isAutoRotation = false } )

Could there be any problem with this setup? It has been working fine for years however I will now update the app with 2017.3184.

Is it OK to keep using this?

#2

Since you are updating your app, I would recommend that you switch to the new one. 

https://docs.coronalabs.com/plugin/vungle/index.html

#3

I can’t speak for Vungle and how long they will support their old plugin, but I would recommend updating to the new one since it’s been out since the middle of last year:

https://coronalabs.com/blog/2017/07/25/updated-vungle-plugin-v5-1-with-new-features/

Rob

#4

If you do switch, be sure to read the docs carefully as your code will need to change. 

The biggest changes I noticed are

  1. You are now required to use a placement ID.
  2. isCachedAdAvailable() is no longer documented, but still exists.  However calling it invariably crashes the plugin.  So, you’ll need to use the listener to track whether you have an interstitial ad loaded.
#5

To chime in here… I use Vungle v4 because IMHO the code is much cleaner and not event-dependent.

Removing such a handy function like isCachedAdAvailable() is definitely a backwards step for sure!

I have been explicitly told that v4 will stay so carry on using it :slight_smile:

#6

Since you are updating your app, I would recommend that you switch to the new one. 

https://docs.coronalabs.com/plugin/vungle/index.html

#7

I can’t speak for Vungle and how long they will support their old plugin, but I would recommend updating to the new one since it’s been out since the middle of last year:

https://coronalabs.com/blog/2017/07/25/updated-vungle-plugin-v5-1-with-new-features/

Rob

#8

If you do switch, be sure to read the docs carefully as your code will need to change. 

The biggest changes I noticed are

  1. You are now required to use a placement ID.
  2. isCachedAdAvailable() is no longer documented, but still exists.  However calling it invariably crashes the plugin.  So, you’ll need to use the listener to track whether you have an interstitial ad loaded.
#9

To chime in here… I use Vungle v4 because IMHO the code is much cleaner and not event-dependent.

Removing such a handy function like isCachedAdAvailable() is definitely a backwards step for sure!

I have been explicitly told that v4 will stay so carry on using it :slight_smile: