New apps and app updates with the admob plugin will be rejected from Google Play starting August 1st, 2014!

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

Hi Corona,

Google is deprecating the standalone Google AdMob SDK on August 1st, 2014 (see http://googleadsdeveloper.blogspot.com/2014/02/since-joining-google-play-services-back.html). They say they won’t accept apps into the google play store that use this SDK starting on that date. If I understand it correctly, this is what the Corona admob plugin uses.

I know you have a newer version of the plugin named admob-v2 that uses the Google Ads compliant Google Play Services SDK; however, this plugin is not available with the current public release build number 2189.

Since I would like to continue to submit apps to the Google Play store with admob after August 1st, can you all please make a public release that supports the admob-v2 plugin before this date?

#2

Hi Corona,

same worries here. Please inform us on your plans on having a new public release compliant with the Google Play Services SDK. There are only few days left 'till August 1st!

#3

Hi guys,

We’re fully aware of this deadline and we’re working hard to ensure that the transition will be smooth and that users will not be adversely affected.

Thanks,

Brent

#4

I understand that updates to our apps will now require the latest AdMob SDK after August 1st, but will apps that are already in the App Store with the older AdMob SDK continue to work with their ads after August 1st if we don’t update them?   Or do we need to update them before August 1st for the ads to continue working?   

#5

The ads will continue to serve according to the article I linked in my first post here.

#6

Thanks, I just wasn’t sure when I read that page, was a bit confusing.

#7

Glad to be of help. Now if only corona would let us know when the next public release will be so we don’t have to worry about the old sdk anymore… :slight_smile:

#8

OK another stupid question.  When we change the line in build.settings from “CoronaProvider.ads.admob” to “plugin.google.play.services” to use AdMob V2, will this change also work on iOS?   Or will I need to keep another version of a build.settings file for iOS builds, which would use the old CoronaProvider.ads.admob?

I just have a Basic account at the moment so cannot test this.

#9

The new public build is out.

The change to build.settings should be all you need.

Rob

#10

And do we need a different build.settings for iOS?

#11

Works fine on ios with just the new line in the build settings replacing the old one.

#12

Thanks @dislam

#13

Hi Corona,

same worries here. Please inform us on your plans on having a new public release compliant with the Google Play Services SDK. There are only few days left 'till August 1st!

#14

Hi guys,

We’re fully aware of this deadline and we’re working hard to ensure that the transition will be smooth and that users will not be adversely affected.

Thanks,

Brent

#15

I understand that updates to our apps will now require the latest AdMob SDK after August 1st, but will apps that are already in the App Store with the older AdMob SDK continue to work with their ads after August 1st if we don’t update them?   Or do we need to update them before August 1st for the ads to continue working?   

#16

The ads will continue to serve according to the article I linked in my first post here.

#17

Thanks, I just wasn’t sure when I read that page, was a bit confusing.

#18

Glad to be of help. Now if only corona would let us know when the next public release will be so we don’t have to worry about the old sdk anymore… :slight_smile:

#19

OK another stupid question.  When we change the line in build.settings from “CoronaProvider.ads.admob” to “plugin.google.play.services” to use AdMob V2, will this change also work on iOS?   Or will I need to keep another version of a build.settings file for iOS builds, which would use the old CoronaProvider.ads.admob?

I just have a Basic account at the moment so cannot test this.

#20

The new public build is out.

The change to build.settings should be all you need.

Rob