Re: Can I Upload My App On Play Store For Free
Benedicte Mansukhani
Here's what worked for me:After getting the error on play console. Now use 'Add from Library' option instead of 'Upload', and you will find your appbundle that failed to upload there, select it and proceed with further steps.
This problem comes out due to multiple gmail logins on same browser, if the developer account is not the default logged in account. You can solve this by signing out all gmail accounts and login in the specific gmail account.
For my case clearing data, using Incognito or changing browser did not work. So, finally I uploaded an APK file (all previous versions were AAB files) and surprisingly Google Play console accepted it!
For me, none of the mentioned solutions worked. The issue was that one of the closed testing tracks had an older APK which didn't target API 33, and the target API update duration was overdue. Make sure that all tracks are targeting at least the minimum API version specified by Google.
If your zip align is not successful or verification failed at the end of the zip align process, this error is likely to occur. Please analyze whether zip align was successful. Also, you can try uploading both in .apk and .aab format. You are more likely to get a more detailed error hinting a possible cause.
I'll chime in because I had the same error. I was uploading an APK and I got the same error. My browser was Firefox.When I changed to Safari the error changed to something along the lines of:Please reduce the size of your APK to 100MB.
Upload failed
You uploaded an APK or Android App Bundle that is signed with a key that is also used to sign APKs that are delivered to users. Because you are enrolled in App Signing by Google Play, you should sign your APK or Android App Bundle with a new key before you upload it.
I'm completely stumped, as I generated a new key for this app bundle at the time of generating the app bundle, i.e. through the Build > Generate Signed Bundle / APK... menu item in Android Studio, so it is a brand new key, unused by other apps.
I've even tried creating a whole new keystore with a new key in it, but always get the same error. Is this some quirk someone else has come across?
When enrolling for App Signing by Google Play for this app, I chose the "Let Google manage and protect your app signing key (recommended)" option, and from all the documentation I've read, the key that you use to sign the app with first becomes the "Upload Key", so it seems like I'm doing everything correctly, but no dice.
I am facing the same issues, in my case signingConfig was setup, I made one simple mistake, that I forget to change app debuggable to false. so even though I generated from menu or from gradle command, build was successfully generated but it was debuggable so play store not accepting signed apk and give me and message like Upload Failed The Android Bundle was not Signed in .
Well, after a lot of screaming and shouting, including reaching out to Google Play Console support in chat (they're only first level support, so... not much help) and email (who put me in the too hard basket and said they can't offer support for app development - what? the problem is to do with uploading an app to Play Console, not app dev!), I discovered this self answered question
Basically, make sure you're doing a Clean & Rebuild Project whenever doing anything to do with signing in Android Studio. For some reason it thought my new app was using the key from my old app and kept signing with that. (I guess the solution was app development support after all!)
What happened is that you must have created another app, signed it with that keystore, and uploaded it to the Play Console, thus making it a key used to sign APKs served to end users. At the same time, you created another app which you enrolled in Play Signing: for this app, the upload certificate is extracted from the first APK you upload. Since you signed that APK with Studio as well, the same keystore was used. Play detected that it was the same certificate for both those apps, and since you used the same key for two different purposes (app signing key for your first app, and upload key for your second app), Play rejected it. The reason is that an app signing key is much more important than an upload key (the latter can be reset while the first one can't), so you shouldn't use them for two different purposes.
In other words, you'll need to create a different keystore to sign your apps enrolled in Play Signing (ideally, one per app), and make sure you never use that keystore as an app signing key for another app.
Keep in mind that this error is ambiguous and could be caused by a number of issues as visible in the other answers on this page. I had originally uploaded my app using the release build variant. Forgetting what variant I had used originally, I tried to upload the debug build variant and got this error.
The other way this can happen is if you have a signingConfig set up in the app build.gradle. It doesn't seem to matter what you specify in the signing section when you're making a bundle - even if you make a new one or choose some other keystore - it will use the one specified in the gradle file.
I had same issue with a project that has many apps and many kotlin libraries. All those apps have dependencies to those kotlin libraries, so this is reasonable configuration.When I released first app in Play Console I created keystore and one key that I used with this first app. When I tried to release second app I got this error. There was nothing bad with signing configuration. To get second app released I had to make second key to keystore and sign second apps bundle this this second key.
Error message "You uploaded an APK or Android App Bundle that is signed with a key that is also used to sign APKs that are delivered to users. Because you are enrolled in App Signing by Google Play, you should sign your APK or Android App Bundle with a new key before you upload it." is very confusing about the situations, but advice how to fix problem was exact right, I has to create new signing key for second app.
I had the same problem. I was working on Godot Engine.The solution was to uncheck the Export with debug option while saving the .aab fileAssuming you've already put in the release.keystore with user and password in the export dialog.
In order to upload an Android play store app, a developer dashboard is imperative. Google Play console is kind of a backend controlling center, from where developers submit Play Store apps for Android. There is a one-time fee of $25 by which a developer can open an account, loaded with functions and control features. After paying this one-time fee, you can submit apps to Google Play Store for free.
In this step around how to upload an app to the play store, you are required to fill out all the information and details you have already prepared with caution before. The table below shows what information you need to fill in the app listing-
Make sure to use appropriate keywords in your app description to increase the chances of your app showing up in searches. Along with this, make sure to use all the data we have talked about in the prerequisite section for app listing.
Moreover, assigning a price to your app is crucial. If you want your app to be free, make sure that this decision is permanent, as Google does not allow you to convert free apps into paid ones. Although, the price of the app can be altered.
There are certain practices such as user interaction and visual design services, working on the latest technologies, localization, etc. that helps your app to get featured. Getting featured on Google Play Store apk can benefit your app to an extent that it increases the attention of users on your app by multi-folds.
Press-release is another way through which you can promote your brand. With this, your brand will come into limelight and many publications will cover your app release which will eventually allow your app to reach a wider user base and develop an authentic connection.
A press release that covers the words, attributes and insights of the mobile app developers and application itself has proved to be an incredible app marketing strategy. It is a great example to show users that what they expect is good.
You cannot just publish your application on the app store and let it be. You need to efficiently maintain your application and introduce frequent updates, attending to the issues and bugs faced by users. Maintaining something is a constant task rather than a one-time thing. So, make sure you keep your app updated with the latest app stack and fix whatever needs fixing.
App Store Optimization is a celebrated practice among all the top Android app development companies. Famously known as ASO, it primarily focuses on the activities which target aspects that can generate more attention and visibility of your application on app store. These practices are focused on increasing the conversion rate of impressions into downloads on the application.
There is no fixed time limit for publishing an application on Google apps store. Though the process of submitting an application through the Google Play Store Console is simple and concise, the duration of your app getting reviewed and selected can vary between hours and days.
We hope that the above instructions were helpful in guiding you through the process of how to upload an app to the Play Store. Once you upload an app to the Play Store, you require an active marketing strategy to attract the customers. After the android app is published, your app requires continuous efforts to make it a success, or competition will overshadow it.
At Appinventiv, we have experts that can turn your app idea into a success story. Be it building a robust and scalable app or publishing it and thereafter, getting it featured on the Google Play Store, our experts can help you in all ways.
All the personal information that you submit on the website - (Name, Email, Phone and Project Details) will not be sold, shared or rented to others. Our sales team or the team of mobile app developers only use this information to send updates about our company and projects or contact you if requested or find it necessary. You may opt out of receiving our communication by dropping us an email on - in...@appinventiv.com
d3342ee215