How to Resolve Common Google Play Errors for Secured Apps
During the process of deploying an application to Google Play Store via Appdome, you might encounter one of these common Play Store deployment errors:
- “APK specifies a version code that has already been used”
This means the version code of your APK, is already in use by another deployed APK.
Appdome Offers Changing the Version code seamlessly, using Context™ in the Google Play Store.
- “No application was found for the given package name”
This means your application does not exist in the Google Play Store.
You must create an application in Google Play Store before deploying it.
- ‘You Cannot deploy a release to “In Progress” state, before it has a “Completed” release.’
Setting a release status to “In Progress“, means the release is rolled out to a fraction of users.
The rest of the users would fallback to a previous release.
This error occurs if a previous release does not exist for the selected track
- “You are trying to deploy a different app than the previously deployed app: Artifact upgrade problem with <version code>”
This means the artifact (APK), you are trying to upload to the Google Play Store cannot upgrade the previous version of this artifact (APK).
This error usually happens, due to downgrade of “targetSdkVersion” or “minSdkVersion”.
Related Articles
- How to Use Appdome’s Build-to-Test Service
- How to Troubleshoot Secured Android Apps Using ADB
- Appdome Diagnostic Logs for Troubleshooting Secured iOS Apps
If you have any questions, please send them our way at support.appdome.com or via the chat window on the Appdome platform.
Thank you!
Thanks for visiting Appdome! Our mission is to secure every app on the planet by making mobile app security easy. We hope we’re living up to the mission with your project. If you don’t already have an account, you can sign up for free.
