Understand Android builds, signing, and app publishing
Creating an Android app involves a build, a signing identity, testing, and distribution. Ethion brings the build artifacts, signing credentials, and deployment requests into your application overview so you can follow those steps in one place.
Updated
APK and AAB serve different purposes
An APK is an installable Android application package. An Android App Bundle, or AAB, is a publishing artifact that Google Play uses to generate APKs for different devices. You do not install an AAB on a phone in the same way as an APK.
Download the signed Android APK as soon as it appears in Manage Application, even while the AAB is still preparing. The unfinished artifact remains pending; you do not need to wait for the whole workflow to finish to test the APK.
Keep the Android signing identity secure
Android signing connects an app artifact to a signing identity. Ethion provides signing credential management and downloads for your Android application. Keep exported credentials private and retain the information needed for future releases.
App signing keys and upload keys can have different roles when using Play App Signing. Check which signing configuration applies to your distribution process before replacing a key or submitting an update.
Use build status to decide the next action
Status colors describe the current build: Green: Success, Finished; Red: Failed, Signing failed; Amber: Dispatching, New, Cancellation pending, In progress, Action required; Blue: Signing, Deploying; Gray: Canceled, Skipped, Deleted. A previous deployment does not turn a canceled or failed build into a successful one. Read any build error or action request before starting another build.
Track your build from Dashboard or My Applications and use Refresh status for the latest result. Manage Application also refreshes active builds automatically and shows the browser preview when available. A preview is separate from a downloadable build or a published store listing.
Prepare for managed app deployment
- Download and test the available APK with your real branding and content.
- Review the app description, customer support information, and data practices.
- Confirm that the required signed artifact is available and that your app's content is ready for review.
- Request deployment from the application overview when the deployment action is available.
- Follow the deployment status and respond to any information required during the store review process.
Store review remains a separate decision
Ethion offers managed store submission and review follow-up. Store availability and approval depend on each store's review and requirements. Submission does not guarantee approval, a specific launch date, or a particular store ranking.
For an update, confirm the version and build numbers and retest the app before submission. Preserve the signing identity required by your distribution process so that an update can be associated with the existing application.
Frequently asked questions
- Why can I see an APK before the AAB is ready?
- Download the signed Android APK as soon as it appears in Manage Application, even while the AAB is still preparing. The unfinished artifact remains pending; you do not need to wait for the whole workflow to finish to test the APK.
- Does Finished mean my app is already in Google Play?
- No. A finished build and a deployment request are separate steps. Use the application overview to test artifacts and request managed deployment.
- Can Ethion guarantee that a store will approve my app?
- Store approval is decided by the relevant store. Ethion provides managed submission and follow-up, while availability and approval depend on the store's review and requirements.