usally when you get a Warning
you get a week or so to update
i hade old Phone gap /cordova app that got a warning
it was crap so i removed it
but stil the warning is displayed
there is a from you can fill out to tell them you have fixed this
but im hopping for the robot to return soon and auto fix the warning :)
mine took 6 hours i think, i updated at night, when i woke up it’s gone.
build 1202
It worked! The notices all got removed!
ok time for me to redo my update then
is it this one you have used ?
http://developer.coronalabs.com/release/2013/1202/
JBean
did you have the version warning ?
“Previously active APKs supported more devices than those in the draft configuration. Some devices will not receive upgrades”
I used version 2407
No it was a different warning, but I don’t have it anymore to show you - something to do with api, I can’t recall the whole thing.
But using 2407 and just updating the app removed the warning.
I think I misunderstood your question - I don’t recall ever having that warning.
wow now its gone
i guse if its not gone in 5-6h something is wrong
my first update was 3 days a go but that dident do anything
did a new before i went to bed with the lates daily build and now it fixed 
Great! Glad you got it resolved!
Hi guys, I’ve got the same issue. I use Inner-active for my ads, and everything has been fine until now. I’m using Starter v2014.2393. I’ve rebuilt my apps and redeployed them a week ago, but still the warning message remains. Please help!
"We have identified a potential advertising ID policy violation with your app(s). "
i have update about 15 of my apps now
the waring goes away when the new version is relased to the store (after the cache is relased about 5-6hours)
i hade problem with one of them
but after moving to google payment API 3.0 (dont know the exact name) also this app got cleard of the warning
so in short if the warning is not gone after ~10hours after your update something is wrong
sorry for the bad english 
Thanks Jedi, but I’m still having the issue - even after recompiling. Is there someone from Corona who can help with this question please?
Hi @will_fourie,
Can you please list all of the plugins that you’re using? Or better yet, post the contents of your build.settings file?
Thanks,
Brent
Thanks Brent! This is what my build.settings file looks like.
settings =
{
android =
{
usesPermissions =
{
“android.permission.INTERNET”,
“android.permission.ACCESS_NETWORK_STATE”,
“android.permission.READ_PHONE_STATE”,
},
versionCode = “3”,
versionName = “1.2”
},
– plugins =
– {
– -- key is the name passed to Lua’s ‘require()’
– [“CoronaProvider.ads.admob”] =
– {
– -- required
– publisherId = “com.coronalabs”,
– },
– },
plugins =
{
– key is the name passed to Lua’s ‘require()’
[“CoronaProvider.ads.inneractive”] =
{
– required
publisherId = “com.inner-active”,
},
},
orientation =
{
default = “landscapeRight”,
},
}
Hi @will_fourie,
So it appears that the only plugin you’re using is Inneractive? It’s possible that their plugin has not been updated to account for various changes on the Google side (acceptance of apps). Can you attempt to contact them and ask if anything has changed in their overall SDK which would relate to the Corona plugin as well?
Thanks,
Brent
I have a question - did anyone get notifications on apps that were unpublished? If so, did you not take action? If so, did they eventually remove the app, or what happened?
I can understand flagging apps that are live, but they are also going through and flagging some that have been unpublished which is quite annoying.
I had apps that didnt even contain the inneractive reference flagged and where unpublished.
I just uploaded an empty apk with just the bare bones to get it to build, published it for 5 seconds and unpublished it.
Within 24 hours the warning had gone.
for some of our apps the flag is now visible again. Any news on this issue?
Inneractive never upgraded their plugin to 64 bit so I’m pretty certain that they’ve not handled the Google requirements either. I would recommend considering a new ad provider if you’re concerned that Google will push the issue.
Rob
for some of our apps the flag is now visible again. Any news on this issue?