admob-v2 build problem with 2014.2189 (2014.3.6) - Error: Get plugin failed.

[BorisB]

The build failes for admob-v2 with the following error:

Error: Get plugin failed.
Publisher: com.coronalabs
Plugin: plugin.google.play.services

build.settings:

    plugins =     {         ["plugin.google.play.services"] =         {             publisherId = "com.coronalabs"         },     },

The same code with admob (V1) [“CoronaProvider.ads.admob”] is building and showing the ads as expected.

Any advices?

[SP_Technolab]

admob-v2 uses the latest version of the AdMob SDK and only works with build 2014.2264 or later.

Best Regards,

Team, SP Technolab

www.sptechnolab.com

[ToeKnee]

@BorisB - Can you provide some more details.

“The same code with admob (V1) [“CoronaProvider.ads.admob”] is building and showing the ads as expected.”

So does this mean you changed over to the new Admob (from legacy (old Admob)) and it works when using corona admob plugin V1?

Or are you still on old admob - tried to use V2 plugin - b/c you only have access to 2189 -  it failed thus you went back to V1 which originally worked.

I am currently holding off changing to the new admob ( not plugin V2 ; actual admob site) - due to the concern that it could result in trapping me in a corner. 

e.g.    Have new admob ids - which may not work with the V1 plugin!

Thanks for any info.

T.

[BorisB]

@ToeKnee

@BorisB - Can you provide some more details.

“The same code with admob (V1) [“CoronaProvider.ads.admob”] is building and showing the ads as expected.”

So does this mean you changed over to the new Admob (from legacy (old Admob)) and it works when using corona admob plugin V1?

Or are you still on old admob - tried to use V2 plugin - b/c you only have access to 2189 -  it failed thus you went back to V1 which originally worked.

I am currently holding off changing to the new admob ( not plugin V2 ; actual admob site) - due to the concern that it could result in trapping me in a corner. 

e.g.    Have new admob ids - which may not work with the V1 plugin!

Thanks for any info.

T.

@ToeKnee - The problem in my case is that I’m using the 2014.2189 (2014.3.6) build.

As SP Technolab mentioned (and the docs as well - shame on me) admob-v2 uses the latest version of the AdMob SDK and only works with build 2014.2264 or later.

There was no need to change anything at admob site. I just changed the corona plugin back to v1as described (see http://docs.coronalabs.com/plugin/ads-admob/index.html).

Best, Boris

[ToeKnee]

Hi Boris,

Some confusion here i think.

There are actually 4 factors to consider in this problem. 

1. corona plugin V1

2. corona plugin V2

& then Admob its setup

3. have an old Admob account - which is called legacy (which will stop in August 2014)

4. new admob (which will be good post august 2014)

When i look at my account on admob - i go to a site www.admob.com/my_sites   - (this i am pretty sure is legacy)

And there is a banner at the top warning of the impending Stop.

The new website address for new admob i think is different.

So are you like me legacy and V1 plugin

or

new admob and V1 plugin?

Thanks T.

[BorisB]

@ToeKnee

Hi Boris,

Some confusion here i think.

There are actually 4 factors to consider in this problem. 

1. corona plugin V1

2. corona plugin V2

& then Admob its setup

3. have an old Admob account - which is called legacy (which will stop in August 2014)

4. new admob (which will be good post august 2014)

When i look at my account on admob - i go to a site www.admob.com/my_sites   - (this i am pretty sure is legacy)

And there is a banner at the top warning of the impending Stop.

The new website address for new admob i think is different.

So are you like me legacy and V1 plugin

or

new admob and V1 plugin?

Thanks T.

I do not have that problem (explained above) with admob and will be forwarded to https://apps.admob.com/  after I logged in.

As said I am using the corona admob v1 plugin.

You may want to start a new topic as I cannot help you.

Best, Boris

[SP_Technolab]

admob-v2 uses the latest version of the AdMob SDK and only works with build 2014.2264 or later.

Best Regards,

Team, SP Technolab

www.sptechnolab.com

[ToeKnee]

@BorisB - Can you provide some more details.

“The same code with admob (V1) [“CoronaProvider.ads.admob”] is building and showing the ads as expected.”

So does this mean you changed over to the new Admob (from legacy (old Admob)) and it works when using corona admob plugin V1?

Or are you still on old admob - tried to use V2 plugin - b/c you only have access to 2189 -  it failed thus you went back to V1 which originally worked.

I am currently holding off changing to the new admob ( not plugin V2 ; actual admob site) - due to the concern that it could result in trapping me in a corner. 

e.g.    Have new admob ids - which may not work with the V1 plugin!

Thanks for any info.

T.

[BorisB]

@ToeKnee

@BorisB - Can you provide some more details.

“The same code with admob (V1) [“CoronaProvider.ads.admob”] is building and showing the ads as expected.”

So does this mean you changed over to the new Admob (from legacy (old Admob)) and it works when using corona admob plugin V1?

Or are you still on old admob - tried to use V2 plugin - b/c you only have access to 2189 -  it failed thus you went back to V1 which originally worked.

I am currently holding off changing to the new admob ( not plugin V2 ; actual admob site) - due to the concern that it could result in trapping me in a corner. 

e.g.    Have new admob ids - which may not work with the V1 plugin!

Thanks for any info.

T.

@ToeKnee - The problem in my case is that I’m using the 2014.2189 (2014.3.6) build.

As SP Technolab mentioned (and the docs as well - shame on me) admob-v2 uses the latest version of the AdMob SDK and only works with build 2014.2264 or later.

There was no need to change anything at admob site. I just changed the corona plugin back to v1as described (see http://docs.coronalabs.com/plugin/ads-admob/index.html).

Best, Boris

[ToeKnee]

Hi Boris,

Some confusion here i think.

There are actually 4 factors to consider in this problem. 

1. corona plugin V1

2. corona plugin V2

& then Admob its setup

3. have an old Admob account - which is called legacy (which will stop in August 2014)

4. new admob (which will be good post august 2014)

When i look at my account on admob - i go to a site www.admob.com/my_sites   - (this i am pretty sure is legacy)

And there is a banner at the top warning of the impending Stop.

The new website address for new admob i think is different.

So are you like me legacy and V1 plugin

or

new admob and V1 plugin?

Thanks T.

[BorisB]

@ToeKnee

Hi Boris,

Some confusion here i think.

There are actually 4 factors to consider in this problem. 

1. corona plugin V1

2. corona plugin V2

& then Admob its setup

3. have an old Admob account - which is called legacy (which will stop in August 2014)

4. new admob (which will be good post august 2014)

When i look at my account on admob - i go to a site www.admob.com/my_sites   - (this i am pretty sure is legacy)

And there is a banner at the top warning of the impending Stop.

The new website address for new admob i think is different.

So are you like me legacy and V1 plugin

or

new admob and V1 plugin?

Thanks T.

I do not have that problem (explained above) with admob and will be forwarded to https://apps.admob.com/  after I logged in.

As said I am using the corona admob v1 plugin.

You may want to start a new topic as I cannot help you.

Best, Boris