You can find answers to many questions about publishing apps in the Play Console Help Center, and our support team can help with the rest.Questions about developing apps
Apps enrolled in app signing by Google Play
Here are some common reasons why you might need to create a new upload key:
- Lost or compromised private key
- There wasn’t an upload key created for an existing app
Apps not enrolled in app signing by Google Play
If you lose your keystore, you’ll have to publish a new app with a new package name and key. It’s a good idea to update your original app to let users know about your new app, and unpublish it to prevent future downloads.
Note: We’re unable to delete apps or let multiple apps have the same package name.
Learn more about certificates & keystores
For detailed information about certificates, keystores, and signing your app, visit the Android Developers site.
If you’re having issues uploading files, you may be having issues with your browser.
For the best experience with the Play Console, we recommend using Chrome. To help troubleshoot issues, make sure that you’re using the latest version of your browser.
If you’re already using the latest version of your browser, here are some solutions to common issues:
- Clear your browser’s cache and cookies.
- If you’re not using Chrome, try using it or a different browser.
- If you have browser extensions or plugins installed, they could be causing conflicts with the Play Console. Try disabling the extensions or plugins, and then enable them one at a time to identify any potential conflicts.
- If you have antivirus or firewall software installed, it might cause issues with uploading APK files or images. If you’re having issues uploading files, try temporarily disabling the software and trying again.
Scan your app for issues
If you continue having issues when uploading your app, you can use Android Lint to scan your app for potential issues. With Android Lint, you can check your app for a wide variety of issues using a command line interface, Eclipse, or IntelliJ.
Test the features required by your app
If you want to see how Google Play will filter your app based on its declared features and permissions, use the
aapt tool, which is included in the Android SDK.
By using the
dump badging command, aapt will parse your application's manifest and apply the same rules as used by Google Play to determine the features that your application requires.
Still having issues?
If you’re still unable to upload files or publish your app, please contact our support team. Include any details about your issue, including screenshots, aapt badging output, and your APK file.
If you’ve recently published an app or update, It can take a few hours for your changes to show on Google Play. Also, make sure your app is published to production or in an open test.
To troubleshoot specific issues, visit app visibility & discovery issues.
As part of the Developer Distribution Agreement, users get unlimited reinstalls of each app they’ve downloaded on Google Play. As a result, apps with installs can’t be permanently deleted. However, to prevent new users from downloading your app, you can unpublish it at any time.
If your app hasn't been installed on any devices, contact our support team to request that your app's data be permanently deleted.
To troubleshoot issues with uploading graphic assets, make sure to upload files that meet the file size, dimensions, and file type requirements for each type of asset. If your files meet all requirements, and you’re still having issues, try using a different browser.
In some cases, if you have antivirus or firewall software installed, it might cause issues when uploading images. If you’re having issues uploading files, try temporarily disabling the software and trying again.
To learn how to release an app update that reaches a percentage of your users that you can increase over time, visit our Help Center article on using staged rollouts.
To learn how to test your app with specific groups or run an open test with Google Play users, visit our Help Center article on setting up open, closed, and internal tests.