Error -24 Google Play app android - android

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.

Related

app updates not showing in the Google Play Store

I have pushed a new version of my app.
On google developer console it is published and all old versions are unpublished but on Google Play Store it is still showing old version. I uploaded the app 2days before so it should have been updated and on developer console, it is showing as updated.
I already clear play store cached and data but still showing old app version don't know why.
I have checked, on all devices showing old versions. does anyone know why this is happening??
I had chat with google support and as per chat they have made some changes to the review process, so it may take more time to review the app thoroughly.
they also said that it usually takes a few hours and up to a few days, depends on different circumstances.
also, they provided the link for refrence
I thought to post it as an answer as if this happens with someone so this would be helpful.
I have also faced this issue. It takes some time to show your app new version on Play Store. They implement it on regional based. So don't worry it will be available in a few hours.

Can't test inApp Transactions with Google App Signing

Inb4 its a duplicate, I know the question is, but they are all older and none seem to help with my issue. Mine seems pretty cut and dry. I have an app that I build with a set of keys and upload to my play console. I have "google signature" enabled so they sign my apps as well. I have products enabled that work when the app is downloaded from google play test track. The SAME EXACT CODE BASE, signed with the SAME EXACT SET OF KEYS I used before uploading to the Play console does not work when I build locally and push it to my device. It says "This device is not configured for transactions" or something along those lines. I'm trying to build out my purchase flows but this is really obstructing me...
Everything is set up according to other answers. Same version code, products active, test track/alpha release are both available. Hell, the purchase flow starts fine when I download the apk from the play store, just not when debugging in AS.
I don't think this is a true answer, or maybe it IS and my symptoms are a bug on googles part, however I seem to have resolved my issue. I'll confirm my answer if this continues to work throughout the day.
For anyone else having a similar issue to me, delete all storage/cache for the app on your phone, then delete the app (NOT USING THE PLAY STORE). Now, install the app from your internal test/alpha track (FROM THE PLAY STORE). Run the app, test the purchase. If it works, close the app and delete all of its storage/cache and the delete the app (NOT USING THE PLAY STORE). At this point you should be able to upload test builds to your devices using Android Studio and have inApp transactions work. Idk why or how this works but YOLO, If it continues to work ill come back and verify this answer. Hopefully this is something google can get streamlined, or maybe I'm doing something wrong and just don't know it. Feel free to answer and I can change my correct answer.

Proper way to republish rejected android app

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!

Unable to push an update to Google Play Store

I'm trying to push an update in the Play Store and I came across the following error. I'm aware of the new target API requirement which will be in effect from November 1st, but as of now, I'm supposed to be able to push an update to play store right? If that's the case, I'm not sure why am I getting this error.
Could some one please help me?
Thank you
That's a warning, not an error. It even says "Warning" right there.
You should be able to publish it anyway. The August deadline only applies to new apps.
This warning does not (or should not) have the capacity to block your release. There are two possibilities:
your release is being blocked by some other error as well which you aren't noticing because of this warning
there is a bug in the Play Console
If it is the second option you should report it to the Play Console support team. You can contact them via the help menu in the Play Console, which is behind the "?" (Question Mark) icon. But the first option is more likely.
I contacted Google Play Store support and they told me the issue is caused because of the version code number of the app. Though I updated the version, I forgot to update the version code number.
I fixed the version code number and uploaded the APK to the play store and it worked.
Thank you

Google Play Store apk update

I had updated my apk file and build a new version (upgrading the versionCode and versionName).
The files was successfully uploaded on the apk 2 days back, but still it is not updated :(
Can some one pls help me.
Its still showing "Processing update" as status on the console.
I tried un-publishing the app and re-publishing the same, it made thing even worse.
Now M unable to search my application.
Tried contacting the google guys, but still no progress.
Please help
Found a similar qstn here
My android app is not being updated on the Google Play Store
For a new app you need to have patience. It may take anything from 2 days to a week. There will be reviews and automated policy checks etc happening after which it will be available on store.
By republishing you just restarted the whole process.
Usual process may take maximum one week. Here only you can do is wait till they respond.
The chances are there the app may be rejected for the update, due to some technical reason. Keep on checking the status change. Also create a query to Google.

Categories

Resources