Preflight and upload
What preflight solves
Preflight finds deterministic issues early: unreadable packages, mismatched Bundle IDs, invalid signatures or Profiles, unusable versions, incorrect target Tracks, or missing release materials. It cannot replace the Provider's final server-side validation or human review.
A reliable upload workflow
- Import the package under the correct Provider and app.
- Read the actual version, identifiers, signature, and declarations inside the package; do not infer them from the filename.
- Resolve blockers first, then review warnings.
- Confirm the target environment, testing scope, or release track.
- Start the official upload and keep the app running until the task reaches a recoverable terminal state.
Provider differences
- Apple uploads IPAs through the Build Upload API, with Build processing, TestFlight, and review continuing in App Store Connect.
- Google Play uses Android Publisher Edit transactions for APK/AAB packages and Tracks.
- HarmonyOS uses AppGallery Connect's package and publishing capabilities.
- WeChat Mini Programs upload or preview through the official local CI.
- Tencent MyApp, Honor, Samsung, Pgyer, vivo, Xiaomi, and OPPO upload packages, submit releases, and query status through their official public capabilities. Their differing requirements for materials, qualifications, and release timing are preserved.
A successful upload is not a completed release
The Provider may continue processing packages, compliance checks, test distribution, or human review. Fox Store distinguishes bytes uploaded, platform processing completed, available for testing, and officially released, rather than presenting an HTTP success as a final store release.