I have an android app that i always upload to google play as an apk with a keystore from 2018 and I use google signing which is recommended as they say, recently I signed the app and exported it as an aab with the same old keystore but now old users can't update the app and new users can't install the app
Can anyone help me please ,is What i did is wrong and if so How to fix it
Related
im trying to upload new application to google play. Already i did this many times so I know process of building/signing with key/uploading and updating apps. Im trying to upload apk and its saying that:
upload valid package of application. Apk was builed and signed with created key.
Thanks for responds.
You need to build .aab, not APK, google announced we have to publish Android App Bundle on Google Play from 01 Aug 2021, for reference I have attached the link below.
Important: From August 2021, new apps are required to publish with the Android App Bundle on Google Play.
Reference Link : https://developer.android.com/guide/app-bundle
I have an app in the playstore created with kodular (similar to appinventor),
I started over with flutter and I like the result
However, when I try to deploy on the playstore, the app is refused with a reason: Your Android App Bundle is signed with the wrong key.
Do I have the upload_cert.der file, and how can I sign the flutter app with that certificate?
(i use android studio)
Your Apps key should match otherwise you will not able to update the apps. You can find the keystore in kodular
Hi I have made a simple app and when I want to test it I connect my phone 1 to computer by USB cable and the app run very good then I share the app to my other phone 2 and other phones from phone 1 and when I try to install it on the other phones it says can't be installed.
Is the issue from phones or from the app I wored if I publish it on Google play
It's doesn't work pls help me.
The error appears because Android Studio signs your apk with the debug.key by default. Documentation is here. When you sign it with the release key as Google Play requires, the problem will go away.
Installing an app on your phone requires that the APK file is signed with a certificate. When you install an app to your phone with Android Studio, it generates a keystore with a certificate and signs your app. This generated keystore is insecure and can only be used for development. Most likely your other phone is not allowing you to install the app signed with this insecure key.
To fix this, you need to generate a certificate to sign your APK with. For instructions how to do this, read the official documentation
I have an application in Play Store. I had to change my PC and I configured everything again in new PC.
Now I generated a new APK and my SHA1 key is changed. Now when uploading a new apk to the play store it gives an error saying Certificate is different from the previous APK.
What should I do?
You cannot push an update to an existing app in Google Play without signing the app with the certificate (SHA1) that was used for the first release.
Now your option is either to find the old signing certificate or you have to release your app as a new app in the play store listing (with a new package name).
Before uploading the updated application, be sure that you have incremented the android:versionCode and android:versionName attributes in the element of the manifest file. Also, the package name must be the same and the .apk must be signed with the same private key. If the package name and signing certificate do not match those of the existing version, Market will consider it a new application and will not offer it to users as an update.
I am developing an app that uses google's turn based multiplayer API. I have two devices that I am using to test on. The first phone, which uses the developer gmail, can sign into the multiplayer just fine. The second one, whether I install the app directly from the computer or I install the signed apk with the release keystore, gets this error every time I try to sign in with it:
Failed to sign in. Please check your network connection and try again.
The second phone uses a gmail account that is set as a testing account for the app in the developer console. I am not positive what the issue is here. And yes, I have made sure that there is not an actual network issue as I am able access the internet just fine.
I appreciate any help. Thanks.
After troubleshooting for a while I realized that my issue was that my SHA1 fingerprint for my signed apk and the SHA1 fingerprint for the project that I had setup in my google developer console were different. To fix this I just unlinked the application from my game and relinked it using the correct SHA1 fingerprint.