What LaunchLayer does not promise
A truthful release guide includes the boundaries: some steps are automated, some are generated assistance, and some always remain external.
No automatic source recovery
Compiled IPA/APK/AAB files are not treated as editable source projects.
No universal one-click compilation
Legacy hosted-wrapper cloud builds are supported through their configured workflow. Source Build V2 inspection exists for arbitrary GitHub/ZIP source, but arbitrary-source V2 compilation is still disabled until the isolated runner/artifact boundary is released.
No automatic native backend
Selecting push, purchases, auth, deep links, wallets, widgets, live activities, or other capabilities does not silently create every external service, server endpoint, provider account, entitlement, webhook, or app-specific code path needed in production.
No approval guarantee
LaunchLayer can prepare, validate, upload, explain, and monitor supported release steps. Apple and Google control processing, policy review, approval, rejection, and publication.
No provider guarantee
GitHub, Apple, Google, RevenueCat, Firebase, and other providers can change APIs, permissions, policies, quotas, processing behavior, and availability.
No replacement for testing
Successful compilation or upload is not equivalent to a working production app. Real-device and store-distributed testing are required for the features your app uses.
No substitute for legal accuracy
Privacy, terms, data-safety disclosures, regulated-content declarations, export compliance, and other legal/compliance answers must match the app's actual behavior and organization obligations.