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.
Ethion shows APK and AAB downloads separately. One artifact may become available before the other. Check the artifact you need and test the appropriate installable build rather than treating every download as interchangeable.
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
A build in progress is still being prepared. Signing means Android artifacts are being processed or awaited. Finished or successful builds can provide artifacts for testing. Failure and cancellation mean the workflow did not complete successfully; review the application details before requesting another build.
Deployment is a separate request. An application marked Deploying is in the publishing workflow, rather than simply waiting for a downloadable build. Check the application overview and any displayed build error for the next step.
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?
- Ethion exposes the two artifact downloads separately. The application may still be waiting for the second signed artifact, so check both download statuses before starting your publishing workflow.
- 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.