Are any Corona plugins going to be affected by Google's change to Advertising Identifier?

We released a new public build today, so that Starter and Basic accounts can take advantage of a build that supports a minimum of Androld 2.3.3 which is a requirement for Google’s’ changes.  Any plugin that has been update to work should now be available to all users.

As for which vendors have updated their plugins, your best bet is to contact them.

Rob

I don’t use any ADS in my apps.

but I got this warning from google play

“We have determined that your app uses a library or SDK (com.inneractive, com.inneractive.api, com.inneractive.api.ads)”

these are old apps from 2013 before the Graphics 2.0 update.

i recompiled using build 2013.1202 , will it fix the issue ?

Anyone who has an idea please advise.

No, 1202 contains the advertising identifier.   You must use the latest public build 2393(Windows, 2393a Mac) if you wish to deploy to either Apple’s App Store or Google Play.

Rob

Hi Rob,

It does not show me the warning notification in google play’s dashboard.

I only used 1202, the reason being the app is not optimized for Graphics 2.0.

I don’t have ADS in the app, and there is nothing in the build settings to initialize any Ads.

Do you think it worked ? because google play’s dashboard does not show the

warning notification anymore.

Its likely that the vendors for the plugins have removed the necessary calls that’s triggering it and that’s why the rebuild took care of it. I see it seemed to just impact inneractive.  Keep in mind that if you ever do move to AdMob, it will require going to Graphics 2.0.

Rob

I got the same notice today, and I used build 2407 to recompile the app, which does NOT have ads, and the notice is still there. I don’t understand how to get rid of it? These are all for my old 0.99 cent apps too.

I have the same notice on an older app as well.  Google said we only had to worry about this new advertising ID on new and updated apps.  My app predates this.  I think the answer for any one who can is to simply rebuild with the latest public build or a later daily build and resubmit.  I don’t understand why you’re still having the error @JBean.  I need to rebuild my app (and its a G1.0 app and I don’t make any money on, so I don’t want to spend energy updating it…) and see if it clears the error.

Rob

I don’t use any ADS in my apps.

but I got this warning from google play

“We have determined that your app uses a library or SDK (com.inneractive, com.inneractive.api, com.inneractive.api.ads)”

these are old apps from 2013 before the Graphics 2.0 update.

i recompiled using build 2013.1202 , will it fix the issue ?

Anyone who has an idea please advise.

No, 1202 contains the advertising identifier.   You must use the latest public build 2393(Windows, 2393a Mac) if you wish to deploy to either Apple’s App Store or Google Play.

Rob

Hi Rob,

It does not show me the warning notification in google play’s dashboard.

I only used 1202, the reason being the app is not optimized for Graphics 2.0.

I don’t have ADS in the app, and there is nothing in the build settings to initialize any Ads.

Do you think it worked ? because google play’s dashboard does not show the

warning notification anymore.

Its likely that the vendors for the plugins have removed the necessary calls that’s triggering it and that’s why the rebuild took care of it. I see it seemed to just impact inneractive.  Keep in mind that if you ever do move to AdMob, it will require going to Graphics 2.0.

Rob

I got the same notice today, and I used build 2407 to recompile the app, which does NOT have ads, and the notice is still there. I don’t understand how to get rid of it? These are all for my old 0.99 cent apps too.

I have the same notice on an older app as well.  Google said we only had to worry about this new advertising ID on new and updated apps.  My app predates this.  I think the answer for any one who can is to simply rebuild with the latest public build or a later daily build and resubmit.  I don’t understand why you’re still having the error @JBean.  I need to rebuild my app (and its a G1.0 app and I don’t make any money on, so I don’t want to spend energy updating it…) and see if it clears the error.

Rob