So I guess I’ll just have to appeal and hope it’s going to work?
Thanks anyways for your help.
How did our icons get in the project in the first place? Was it one of the sample apps we provide?
When going to Corona SDK and creating a new ‘blank’ project, it creates a folder with the 3 files (main, config, build) and the 20 icons.
Well, I didn’t delete these, that’s why it got removed…
I haven’t gotten around to adding my app icons yet, so those files do not exist at all in my project. But when I create a debug build and install that on my device, the app icon is the Corona logo.
Earlier today I created my developer account and uploaded my apk. The icon that showed up next to it was Corona’s logo. After seeing this thread I deleted the apk just to be safe.
But does this mean that I must create my own icon files prior to uploading the apk to Google? Even if it’s still in alpha?
The icons are there so you can see what icons you need to provide. The intent is for you to be place holders and for you to replace them with your own icons. For device testing, you have an Icon to work with. I’m surprised that Google is checking alpha and beta builds, but if they are, you have to adhere to their policies.
Rob
@Vince_ I would, even in alpha. The sad thing is that you can’t really get warnings or anything, you do a thing wrong, you get a strike.
Please don’t do the same mistake as me, at least do a random photoshoped icon (takes 5 mins).
To be honest, I was too lazy to replace icons and screenshots because I was focused on the code and making it work. I thought the app must be published in order to be checked, event though I didn’t know such scanning is taking place. I guess the safest way is to fill all images with any color so Corona’s logo is removed.
Thanks for this posting your unfortunate event, this is important info for anyone considering publishing to Google Play.
BTW, I believe this post should be PINNED at the to of the Android forum and mentioned by any Corona Android Build documentation.
Nail
I’ll see about getting something added to the build guide.
Rob
Also, thanks Rob for looking at possible ameliorations.
I’ve appealed, a bot answered me.
Hi,
Thank you for reaching out to the Google Play team.
After further review, we are unable to reinstate your application. You can find out more information under Reason for Removal in the initial removal notification from Google Play. If your account is still in good standing and the nature of your app allows for republishing; you may consider releasing a new, policy compliant version of your app to Google Play under a new package name.
If you do choose to re-publish a new, policy-compliant version of your app, please make sure to review the Content Policy and visit the Policy Help Center for additional guidance to ensure your next app is compliant with the policy.
Due to the volume of appeals, we will be unable to respond to follow-up queries where we have no new information to share.
Regards,
The Google Play Team
That’s quite sad from google, they are ‘trying’ to help developers, however, a bot won’t help at all. It’s not guaranteed that’s a bot, but I suppose so, I’ve seen the exact same reply on other forums. I have the impression it will answer that automaticaly unless you have a copyright file…
I could think that 25$ would give me the privilege of someone really checking my appeal, apparently not…
Not trying to be negative here, but companies like Google don’t give a sh*t about small developers, unless you’re revenue is 100k a month. It’s sad, but that’s how it works, not only with Google. You’re just a small fly ready to be crushed. 