I am trying to publish my app on the android play store but I can't figure out whats wrong with my app when it comes to the supposed metadata problem I have. How do I fix this and how do I identify the problem as I have have made changes to it multiple times and have resubmitted it for publishing yet I still have the same problem, how do people to this issue? Is there some sort of way which I can find where the exact problem to my situation is?
Related
I am working on client project. I submitted the android app on play store from my account. It was showing on Play store. Than according to requirement i have to publish the app from client play console account. I removed app from my account and published the same app with different package name. Than it shows app rejected because of some family policy violation. I fixed this and resubmit the app. Now it taking a lot of time in reviewing the app.
I have tried to resubmit the app after editing the policies required by google.
I want to know how much time google will take to republish my app after reviewing it again.
Or How i can connect from google with any #support email.
It usually they review my apps within few hours... but... I feel there's something wrong inside Google and one of many emails I had from their support told me it's because there's a new review process for apps on the Family program. Well I will tell a little bit about my journey may give you some idea why you are having this problem.
We experienced this problem with 2 apps:
First App: I received a message saying that my update was rejected because of the violation on the Family program alleging that it was crashing or giving an error (pretty generic message without any detail at all), I enter in contact on the support form and they send an email asking for me to read the terms and to update my APK number and submit again, I read the terms, I already had complied with everything so I replied saying that, we already comply with everyhting and we tested the APK and OBB installation and game play, all good, please send more details, they replied copying and pasting the same message, I once more insisted and asked for them to explain the problem, they replied asking for update my APK version and submit again, I said this will solve no crashes, please explain what is the problem and the support called Sara highlighted in the message asking to update the APK version, kind of talking with a machine that do not responded what I asked, but I updated my APK version, submitted again and... Worked. Why? For some reason they will not explain, my guess is they just marked my APK as dirty as an attempt to remove apps that the developers don't update, there's no other logical thing I can think off.
Second App: This one I didn't had a happy end as the previous one, I tried the technique of updating the APK version 6 times, none worked, I asked help on the form (many times), they just copy and paste the message about read the Terms, I started to insist for some details, provided them with many proves that my APK+OBB files sent to Google Play are working fine, and asked for any clue about this "problem", like a device model and Android Version that they experienced it (isn't the minimum they suppose to provide us?) but after requesting this many times, for the first time the support guy called Arthur didn't copied and pasted and finally wrote an email, his answer was:
Hi Developer,
Thanks again for contacting the Google Play Team.
As much as I'd like to help, due to policy, I’m not able to provide any more information or a better answer to your question. In our previous email, I made sure to include all the information available to me.
If you have a different question about Google Play policies, please let me know.
Regards,
Arthur
The Google Play Team
It means, he has no information at all about what is the problem, I've trying to solve this for 2 months, our flagship game is threatened of been removed from the store and they can't even explain why, the support team can just copy and paste a generic message without any understanding of our problem and we have no other channel to ask for help.
I'm really disappointed with Google for such poor support for developers.
Hope you can solve your problem updating your APK and submitting again, otherwise you can enter on the same loop as me.
Good luck!
I've published multiple apps using flavors and each one have multiple apks using splits. At first few users complain that they getting error 963 when trying to download the app from google play store but now, after version update, the complains number increased significantly. lot of users complains that they get error 963 and cant download the update.
Is there anything I can do from my side to prevent it from happening?
The apks size are ~30MB each and I've added android:installLocation="preferExternal" to manifest.
Removing the android:installLocation attribute from the manifest seems to solve the issue.
Is there anything I can do from my side to prevent it from happening?
No. Some people publish articles how to solve the issue, but this is all from user perspective and is rather working the issue around, not fixing it. You, as developer, cannot do much about how google infrastructure or services work.
I received a complain from admob regarding an specific App that does not belongs to me, saying that the Ads were disabled on it.
Taking a closer look, I noticed that it is related to an App the I have developed and is available on Google Play, but someone changed it's App ID, and put it on a store called 1mobile.com/ ( Probably a store of illegal content ).
Here is my original App on Google Play
And here is the App with a different ID
How can someone do this? How can I prevent this from happening? This could causes someone to loose their admob account.
How can someone do this?
What do you mean, download your app, change AndroidManifest and resign it? Well, it's just that. Download, change one file, resign.
How can I prevent this from happening?
You can use obfuscator and App Licensing but note that anything in your application can be changed, if there is enough motivation for someone to do it. Personally, I learned not to care.
This could causes someone to loose their admob account.
I don't see how. You won't get any money from the stolen copies, that's for sure. But that't about it.
You are everytime helping me but now I couldnt find a good post speaking about my problem (or solving), so I hope you can help one more time...
Recently I uploaded my app to Google Play , everything is all right but when i upload new upgrades some users can´t update the version because they get an ERROR-24
It´s a free online app , when users uninstall the app and they install it again... then it works perfectly...so I am wondering if there is something I can do to fix it!
Thanks everyone!
it´s this error:
http://appslova.com/wp-content/uploads/2014/02/android-error-24-google-play.png
Don't know if this will help you, but the error in my case was due to the sharedUserId value in the manifest being different in my update. Changing the value back to what it was before allowed the update to complete through Google Play. You must always use the same sharedUserId for all updates of an app once it's in the Play Store.
I had a app submitted to google play store and it had been on there a while it was really buggy and i decided to pick back up development on it and completely revamp it.
Problem: i have forgot my keystore sign that i did the first app with so i decided to unpublish it and do a completely new upload of the app under a different name.
Now the new app doesn't seem to be showing on the google play store now matter how hard i look?
With the old app is it possible to delete this or is unpublishing it the right thing to do.
Can anyone give me some steps on possible ways to resolve this or ways in which you can check the status of your app submission?
I also experienced this with some of my apps. It seems that there are some kinds of caching strategies in place that prevent the item from appearing.
Just wait another couple of hours and check your application again. As long as the market says that the app is compatible with your device there shouldn't be a serious error.
The delay isn't consistent at all. It can range from 45 minutes to several hours in my experience. I tend to upload before bed and when I wake up it has appeared. I guess it is one of those "a watched pot never boils" type things
Refer: App not showing up in android market place/google play