Yes, I’m sure 
The documentation needs to be updated since we have the new Android dependency system in place.
I’ll get somebody to look at that. Sorry for the inconvenience.
Thanks Will check that.
Seems I’m still getting that error after removing plugin.google.play.services.
I’ve tracked the culprit to [“CoronaProvider.gameNetwork.google”]. It’s including the old Google Play Services jar which is causing the conflict. I’ll need to talk to the guys to see what can be done.
Thanks, I’ve been tearing my hair out trying to find a workaround. I need a quick update to fix a huge bug that started since the transition to 2017 in my app.
Is there a way to use the old admob plug-in (perhaps with some old build)? I’ve tried 3007 but it still causes this issue. Perhaps I should go further back.
To use the old AdMob plugin you’ll need to remove ‘plugin.admob’.
Also, I think you should be good to go if you use a Corona build < 3005.
Went back to build 2987 which seems OK with the old admob v2 plug-in.
ingemar, thanks a lot for your quick response to my issue! It really helps.
Afraid not. We have leader boards.
Ok. No problem. Just wanted to know so I can give the proper advice.
The thing is that all CoronaProvider plugins are deprecated and are not updated anymore since they have replacements.
CoronaProvider.gameNetwork.google is replaced with plugin.gpgs and is fully backwards compatible so it should just be a matter of changing the plugin specification in build.settings, and the ‘require’ statement in your Lua files.
CoronaProvider.analytics.flurry is replaced with plugin.flurry.analytics. The logEvent() statements are fully backwards compatible. You’ll only need to change one line for init() as it accepts a listener now.
By doing that you should be “future proof” as these plugins are maintained. Also the new plugins have additional functionality should you decide to expand your app to use them.
OK, Thanks. I’ll switch to these new plug-ins and test the new Admob version