Our App Kidstriangle User installation from google play store works fine on Android 4,5,6 but we always get 504 error when install on Any Android 7
1. Already tried clear cache, clear data, login/out from store.
Any idea why this is specific to Android 7 only.
We are using google-play-service GCM:7.0.0 (used for notification) to get maximum comparability is that can be one of the reason?
1. Using latest Android studio and Graddle with targetSDK 25 and compiled with 25.0.3, minSDK 16
The Problem is if you are using android 2.2.2
1. release apk are aleardy algned avoid aligning them again
2. avoid/uncheck v12 full signature while generating the signed apk
Google issue: 504 is generic error that comes after app is being downloaded from google play store and before installation starts. this error code typically is being used to show the issue with google play service. but google is using this error code for non-obvious reason as well that makes user more confusing.
So advice if you are having error code: 504 while installing app from google play store use above two recipe to fix it.
This fixed 504 error for me
So at the time of generating build "Generate Signed APK -> Signature Versions: Select only V1(Jar Signature)"
Related
I'm attempting to publish a new release of my app but I get errors from the Google Play console:
1 Error
error
Error
You can't rollout this release because it doesn't allow any existing users to upgrade to the newly added APKs.
4 Warnings
1 MESSAGE FOR VERSION CODE 4004
Warning
None the of users of this APK will be able to upgrade to any of the new APKs added in this release.
1 MESSAGE FOR VERSION CODE 2004
Warning
None the of users of this APK will be able to upgrade to any of the new APKs added in this release.
1 MESSAGE FOR VERSION CODE 1004
Warning
None the of users of this APK will be able to upgrade to any of the new APKs added in this release.
1 MESSAGE FOR VERSION CODE 5
Warning
This App Bundle contains native code, and you've not uploaded debug symbols. We recommend you upload a symbol file to make your crashes and ANRs easier to analyze and debug. Learn More
Any clue what might be going wrong?
For some reason, your android-versionCode from your current build is lower than the version already available on your Google Play Store.
Change the android-versionCode of your APP to a number HIGHER than the version already available and it will work.!
Strange problem here. I have a deployed application on Google Play. From Google Play Developer Console I'm trying to update the current version of my app with the new apk (version code 22 vs version code 21), however, upload fails with a generic "Upload error" message. I already tried to launch lint command and it builds the project without any error. Does anybody have any idea? Thanks
By contacting the Google Support, they told us that the problem could be related to our DexGuard version. After updating the library to last version (8.1.23), we regenerated the apk and uploaded it without any problem :)
I have also faced same issue few days before. I have solved it by just changing version code and upload it again.
Now if you upload apk with version code 22, change it to 23 and upload it again, hopefully your issue will resolved.
Trying to upload the version 39 of the app, the error message I get is:
Error uploading 'foo.bar.baz'
Version 38 of this app cannot be downloaded by any devices as they will all receive APKs with higher version codes. [403]
Screenshot:
What does this exactly mean? I'm trying to publish as "Alpha" from VisualStudio for Mac (the current version 38 of the alpha channel was uploaded manually.)
The Version number (integer-based) is set via the versionCode in the manifest must be increased each time you submit to the Play Store no matter if it is submitted as an Alpha, Beta, or Release APK.
Either via the Project Options / Build / Android Application :
Or via manually editing the AndroidManifest.xml:
android:versionCode="18"
Seems to be a bug in Visual Studio for Mac, so I reported it here. Hopefully they fix it soon.
If I remember correctly I've had a similar issue when I was trying to update an apk with higher version code to beta, when there was still apk with lower version code in alpha.
Since you are trying to upgrade on alpha, maybe you have an apk on internal test track with version code 38? If that is the case, I would deactivate version uploaded to internal test tract (or update it to version code 39) and then update version on alpha
background:
My current app is already running on Google play with minSdkVersion=8. As every developer knows Froyo and Gingerbread should have died a couple of years ago, and finally the product team on the company allowed us to drop support for them and go to API 15. Yeah.
Approach:
The idea is to leave this last stable version still available for Gingerbread users to download, so what I'm trying is:
create a build with minSdkVersion=8; maxSdkVersion=14; versionCode=195
create another build with minSdkVersion=15; versionCode=250 (skipping a few version codes in case we NEED some emergency maintenance)
the issue:
it all builds fine, but Google Play does not allow the multi-apk upload with the following error:
This configuration cannot be published for the following reason(s):
It is forbidden that a device upgrading from API levels in range 8-14 to API levels in range 15+ should downgrade from version 195 to version 194
question:
is what I'm trying to do something that Google Play does automatically?
is it possible to do what I'm trying to do?
if possible, how?
The problem is maxSdkVersion=14; versionCode=195. This means that if someone has a device running API level 14, and they upgrade that device to 15, the version of the app they have installed (195) will not run.
Try omitting the maxSdkVersion. I'd hope that people in this scenario would then continue to be able to use the 195 build of the app, and then Google Play should upgrade it to the 250 build next time it performs its check.
Google Play does this automatically - users will receive the latest version that is compatible with their device so there's no need to publish your version 195.
As stated in that error, you should continue to have 15+ versions of the app have a higher version number than <15 builds - this will ensure that users only ever upgrade their app to maintain compatibility.
This error message sounds like Goole Play doesn't "see" your second APK (version 250) for API 15+ and it "believes" users with 15+ will have to downgrade to older version 194 when new version 195 gets installed. I never tried to upload multi-APK projects, but documentation says you need to switch into "advanced mode" (a button in the top-right corner) to upload multi-APK. In this mode "upload new apk" works a bit differently. I assume this might be the issue.
I'm trying to publish a new version of my application in Google Play. When I upload new APK file (app version 22) I can't see the option to publish it in production. I can save it only as a draft. There's a red message (see the screenshot below) saying:
Version 20 is not served to any device configuration: all devices that
might receive version 20 would receive version 22
Situation doesn't get any better when I deactivate APK 20 (2.0).
What am I doing wrong? I can't figure it out.
The problem was very silly. I just didn't save my changes in the dashboard using the Publish now button. So in the end I just didn't deactivate the old version which prevented me from publishing the updated one.
Just publish your changes and you're good to go.