Build, upload, TestFlight/Play testing, review, and release
Deployment is a sequence of separate provider states; uploading a build is not the same as publishing it.
Build
A native build compiles the configured project into an iOS or Android artifact. iOS distribution requires Apple signing; Android release output requires the intended package/signing configuration.
Preflight
Before upload, LaunchLayer can compare artifact metadata, project identifiers, configured store application identity, signing/readiness data, and version/build information. Mismatches should be resolved before provider upload.
Upload
A supported direct-deployment job transfers the existing artifact to the provider using configured credentials. Upload success means the provider accepted the transfer request or artifact; it does not mean review or publication is complete.
Provider processing
Apple and Google process uploaded binaries before they become selectable for testing or release. Processing time and provider-side failures are outside LaunchLayer's control.
Testing
Apple TestFlight and Google testing tracks are provider-managed distribution stages. Test the actual store-distributed build, including login, purchases, notifications, deep links, permissions, and any native bridges relevant to the app.
Store listing and declarations
Screenshots, descriptions, privacy disclosures, age/content answers, export/compliance information, data-safety/privacy details, pricing, territories, and review notes must accurately describe the released app. LaunchLayer can assist with preparation but the account owner is responsible for accuracy.
Review and publication
Apple or Google decides whether an app satisfies its current policies. After approval, release may still be manual, scheduled, phased, staged, or otherwise controlled by provider settings. LaunchLayer cannot promise approval or an exact review timeline.