Appodeal - August 19 deadline.

I guess if we make a fresh (32bit) build and update our apps today we will be fine.

Right?

Yes, that is what I am doing. I am getting this sinking feeling that Google is getting ready for their mass purge of 2019. Last year I lost a couple of apps.

You are not alone.

I got the same feeling and google was hard on me too.

Fortunately the “noncompliant” apps were updated and live again in few hours.

Just checked beta and regular versions of Appodeal plugin for Corona:

plugin.appodeal: 1.6.5 (SDK: 2.4.9)  - regular

plugin.appodeal: 1.6.5b (SDK: 2.5.3) - beta

So, the question is how to get SDK: 2.5.4 which Appodeal is recommended to use with Corona? I built app on the last available 32-bit daily build.

the beta should be fine. anything 2.5.1 and above

Thanks!

Hey, how were you able to determine the versions?  I have never been able to get the getVersion() method working on the Corona Appodeal plugin (never returns anything in events or in console).  

I read the deadline agramonte posted and came here to post the same.  I’d love to know what version of the Appodeal plugin the Corona plugin is using…

The version shows up in the console shortly after you load the plugin with the “require” line. 

The version listed by grcool are correct. I asked Appodeal for a list of my apps and what version they were using and they provided a list in a few hours. They should be able to do the same with your apps.

07-20 21:42:40.483: V/Corona(18606): > Class.forName: plugin.appodeal.LuaLoader

07-20 21:42:40.484: V/Corona(18606): < Class.forName: plugin.appodeal.LuaLoader

07-20 21:42:40.484: V/Corona(18606): Loading via reflection: plugin.appodeal.LuaLoader

07-20 21:42:40.485: I/Corona(18606): plugin.appodeal: 1.6.5b (SDK: 2.5.3)

Huh, I’ve never seen that type of information in the Corona Simulator on Android or iOS.  Are you opening using the Corona Simulator? logcat? Any special parameters being used to display that?  Or are you still building in Android Studio?

Your tip on asking Appodeal is priceless, thanks a million.  I’ll do the same.  Appodeal is pretty fast to respond which is nice.

I use simulator builds and monitor. It is a tool inside the Android SDK => tools => monitor. Then I filter by “tag:corona”

I owe you a beer.  Merci, agramonte!

which is the last available 32-bit daily build?

2019.3490

Rob

So, I submitted one of my apps that was flagged for Appodeal version issues and I’m still not able to get it approved.  I’m using the latest daily build and generating 64-bit android packages.  Is the proper version of Appodeal automatically included in these latest daily builds or do I need to do anything to specifically reference that “beta” build of Appodeal?

specifically reference “beta”

Don’t fear the word “beta” in this context. It’s really the “latest” branch.

At some point we probably should clean this up, but in today’s CI/CD environment (Continuous Integration/Development) and with us being open source, it makes more sense for us to think of this plugin this way instead of the context of “alpha, beta, release”.

Rob

I was under the impression that rebuilding would pull the latest plugin.  Is this not the case?  What do I need to do to pull the right appodeal version?

There are three versions of the Appodeal plugin:
 

  1. The original “all inclusive” really massive single plugin. This plugin has not been updated in quite a while. (October 22, 2018, a little over 6 months ago). I’m trying to get clarification, but given it’s size and the in-ability to turn off individual networks that may have code that Google or Apple decides is offensive, I don’t see a lot of reason to use this plugin any longer. Appodeal may feel differently about it, which is why I’m trying to find out more about its long term support.

  2. The modular plugin. This plugin lets you choose which providers you want ads from by including ad modules for them and excluding those that you don’t care for. Naturally if you included all of these ad platforms, you end up with an app as big as the original “all inclusive”, but at least you’re empowered to disable networks on a network-by-network basis.  It’s hard to give an update on when this was update last, as individual ad networks may get updated. But generally, it looks like most of them were updated around 12/2018. Some are older and a couple are newer.  I think the minimal modules were updated to work with 64-bit Android, but if a given network didn’t need a 64-bit slide (i.e. pure Java based .jar library) it didn’t get updated.

  3. The “Beta” module plugin. This plugin gets the most updates. It’s modular like #2. As far as I know it’s the only one that is 100% Compliant with all of Google’s “issues”. This shouldn’t be considered “beta” but “current” and it’s the version you should use today if you want to deploy. At some point in the future, #2 may get updated to bring it up to “beta” level and the “beta” will start getting future updates.

Just visit the doc page and find the build.settings stuff to use the beta version. It’s really simple.

Rob

I recommend the “beta” version too. Gdpr ready, free (we could discuss this more :p), you can disable networks you don’t like (smaller builds) and works flawlessly. It’s also an amazing option for customer’s apps!