Google Play doesn't accept app bundle with any Huawei dependency - android

When I want to upload app bundle to GooglePlay with any Huawei dependency it gives error without any information.
I tried all of these one by one and every time it gave error until I remove all of these from gradle. I tried to add these dependencies to another app and publish however result was same.
However interestingly I can upload APK without any error.

This problem should be caused by Language package problem.
You can go to the application's build.gradle file, in android->defaultConfig, limit the languege resources to what you'd like to use:
android {
defaultConfig {
...
resConfigs "en", "fr" //pick the languages you'd like to use
}
}
Then rebuild the .aab file and try uploading.

APK can you uploaded, but Google play console showing error (red icon) while uploading app bundle. since google console is not showing any tip or error details. If you are using Huawei services HMS core related libraries in your application you need to use the latest
Huawei push services and it will resolve the problem with app bundle upload.
implementation 'com.huawei.hms:push:5.0.4.302'

You can try to upload APK instead of AppBundle. We faced same issue two weeks ago and fix it with uploading APK.

Update:
Push Kit 5.0.2.300 has not fixed the issue yet. The latest version of SDK will be released in November 16 here. Please update it to 5.0.4.302.
This problem is a known bug and it has been rectified already. Please update the HMS Core SDK to latest version here.

Related

UE4.27.1 Unsupported Google Play Billing Version

I have a problem with packaging Unreal project for android and publishing on Google Play Store.
When uploading it shows an error:
We've detected this app uses an unsupported version Play billing. Please upgrade to Billing Library version 3 or newer to publish this app.
I have project configured for Google Play Billing. And in file in engine/plugins/Online the version is set to 3.0.0. I also tried different versions but with no success. Every answer i found was pointing to this file and at this point nothing seems to work.
If anybody faced a similiar issue and knows the answer i would be extremly thankful.
Download this plugin, add it to your project, and enable it in it's settings under Plugins in Project Settings. You don't have to use it or do anything with it. It just includes the library. Can confirm this will pass the Google Play store check.
https://www.unrealengine.com/marketplace/en-US/product/android-play-billing

Error at uploading my React Native/Expo app on Google Play Console

Months ago I uploaded an alpha app that I created using Expo on React Native. I build the app with the version 1.0.0 in app.json. The people involved with the project tested it, I improved it with some other things and we concluded it's ready to go to production.
The thing is Google Play Console returns error when I try to upload it. According to the message (number 2 in the below print), it says (in Portuguese) "You already have an APK or Android App Bunble with version 1 code. Use another code". What does that mean?
Basically, I uploaded it, improved it and now, want to upload it again with the new things.
I tried to upload it in alpha again, beta, build the app again with version 1.1.0 in app.json but, same error message. Has this version 1 code nothing to do with the version in app.json?
In the below print, we can see the main panel, where there is just one release, which is the alpha one. Any help would be great. Thanks for now.
------------------ EDIT -----------------------
According to an answer, I thought it would be good to put the print of app.json. I hid some private fields. As you can see, the version is 1.0.0, but I tried building a 1.1.0 and 2.0.0 version app. None of them solved the problem.
seems like your new app has a versionCode that conflicts with the existing app.
go to YOUR_APP/android/app/build.gradle and search for versionCode. increase the number by 1, recompile your .aab or .apk and upload again.
UPDATED
versionCode is missing. Can you add it like this?
“android”: {
“versionCode”: 2,
...
}

Apk upload on Google Play developer console not working

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.

Android app is crashing due to V/GoogleSignatureVerifier: Signature not valid

I have an android app in which I am using Google Maps API for Android v2. It was working fine in my phone until I upgraded my phone to Marshmallow. After updating my phone once I uninstalled it and again installed it using Android Studio it started having random crash. And every time the error was
V/GoogleSignatureVerifier: Signature not valid. Found:
MIIDDTCCAfWgAwIBAgIEPmxzXDANBgkqhkiG9w0BAQsFADA3MQswCQYDVQQGEwJVUzEQMA4GA1UE
ChMHQW5kcm9pZDEWMBQGA1UEAxMNQW5kcm9pZCBEZWJ1ZzAeFw0xNTA5MjExMjE1MDNaFw00NTA5
MTMxMjE1MDNaMDcxCzAJBgNVBAYTAlVTMRAwDgYDVQQKEwdBbmRyb2lkMRYwFAYDVQQDEw1BbmRy
b2lkIERlYnVnMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAoTlzAY3DX0+vQmRo5stW
izwv76mghc1mbdxQnI16N6Ci/LFPOsiQLfYgt/qqitKCmo2kWWzfKNxN1Qyg5KaFdXRxpM8Ec7Xm
fkMX5cXzJOBDS62uWoDXpjiaXNOBeCvHDwC02EfOGfBd8csnO7sm3htHP8l2Jbn4uAY/zRQ+F4+C
Y477hSMxUvcDYoOoAcsye7pEu1bvPLSRxM44kjjhBFJlLYw6QtzE00khMrwdgBQwSdY0vtUPj9NM
hKGRuGoK/suIpd9e82EhqbUSlYsd62I/HV3390Eo/N2xXCsK7jrRdz6G9MjHfnUQLN80frZXGApl
LWiBti2soI9HhI++dQIDAQABoyEwHzAdBgNVHQ4EFgQU3JFv8ivvt36O8WrsmkXRWYCDbEEwDQYJ
KoZIhvcNAQELBQADggEBAFLFGhfV6F4VOMCdKky6drHD10LzvR8/6QJzf/yp1QARzb3aR319g1my
f6Ffsaam9SKKj6OO92Jz7RTgUvZ6aD5sgRJXKcetmrGNWLGvsg0Rn+OxyEJ6dp4z49Oj5xyXjREp
6zv3QXxENib6EmPYKkFRS6cIe3QOMPsa6Q0KBKQFNnRAW+A+VBAVfEQYB1lgUMXUD+L9pc9EGNcN
zbatMn4FuWeyrhVaiSgMqyNHghUISgAZF76ImkQoPHVwgu7DzQQ44bXAwAbLFIwVhate/C0zN5ps
TjBZ4ojF0Z9mFM9tbLzBYCL2BpNCtYbp9uMpp4YtnX0+2sdxU6vi+ffSeAk=
Looks like updated Google Play services might be causing problem. Help would be appreciated.
This logcat warning is caused by a bug introduced in Google Play Services 9.x. It can be safely ignored, I don't believe it causes a crash, so your crash may be caused by a different issue. The message should go away with a future update to play services.
This issue has been acknowledged by an engineer at Google in the answer to this post.
I had the same issue recently. What caused it for me was when the phone auto updated Google Play Services to version 9.0.83.
The only solution I found was uninstalling the update and allowing Google Play services to re-update.
To remove the update:
Settings > Apps > Google Play services > Hit the three dots and uninstall updates. Then reinstall the updates through the play store.
Start the app and it should ask you to upgrade your Google Play services.
The version was originally 9.0.83 after doing these steps it downgraded to 8.7.03.
I don't feel like this is a solution since I have a few people testing my app and a few of them are having the same issue (the ones on version 9.0.83). I'm not too sure what changed with 9.0.83
I was also getting same exception and I fixed it.
Note: I am working on google analytics and was getting this exception. But my app was not crashing I was getting this in Logs. you can also try this solution.
add this in project level gradle file.
classpath 'com.google.gms:google-services:2.1.0'
and this one for module level gradle file.
compile 'com.google.android.gms:play-services:8.4.0'
and move `below plugin at the end of file (at last line) of module level gradle file.
apply plugin: 'com.google.gms.google-services'
`
I was facing same problem after changing the system and project config.
Try these steps:
Check if you have enabled offline work for gradle: Goto File > Settings > Gradle. Deselect Offline Work if it's checked.
Then confirm if you have latest version of google services mentioned as dependencies in project level build.gradle:
classpath 'com.google.gms:google-services:2.1.0'.You can find latest version here: https://jcenter.bintray.com/com/android/tools/build/gradle/
Clean and build the project after the gradle sync completes.
These steps solved the issue for me. In case you've changed the system used for building this app, make sure to update the SHA1 in your project on Google Developer Console and update the Maps API key in your android project.
What fixed it for me was deleting the debug.keystore file found in the .android folder.
figured it out after reading that the debug.keystore file expires after a year and the system needs you to delete so it can create a new one.
https://developer.android.com/tools/publishing/app-signing.html#expdebug

What is the correct protocol to fix a bug to an already published app on Google Play?

I have an app on Google Play and I tried finding resources on how to "correctly" fix a bug in my app? Do I un publish my app then upload a new APK? I tried this, but I get the message:
"Upload failed
You need to use a different version code for your APK because you already have one with version code 1."
And so I am wondering what is the correct protocol to fix a bug to an already published app on Google Play. That being said, I un published the app currently. Also, I do not feel it's necessary to update the version number because of this minor bug. Any ideas. Thanks!
If you need to update the binary which is in google play store you must increment the version name and version number in Android manifest file. There is no other way to hack this.
Previously versions were maintained in AndroidManifest.xml file. But now in Android Studio it is handled in the app's build.gradle file.

Categories

Resources