'%20transform='translate(102%20102)%20scale(.8)'/%3e%3c/svg%3e){kind=small}
App Distribution
Update a version or add another platform
Update packages in an existing app and distinguish uploaded, pending and published versions.
Before updating
Prepare the new APK or IPA and confirm the app and target platform. Android updates require the same package name; an iOS Bundle ID change needs extra confirmation. Keep recoverable original packages and release notes.
Upload a new package
- Go to App distribution → Monthly apps or Pay-as-you-go apps, open the app and select Update version. To add a missing platform, select Add Android version or Add iOS version.
- For an existing platform, choose the release mode before uploading. Publish now is the default; Save prerelease and Schedule release are also available. Scheduled times use Beijing time and must be at least 10 seconds ahead and within one year.
- Select the package for the platform. After upload and validation, it is submitted automatically using the selected mode. Android package-name mismatches block the upload; iOS Bundle ID changes and replacement of pending plans still need confirmation.
- Adding a new platform still requires Confirm platform. If a monthly app needs a prorated charge, review it before confirming. A failed submission retains the uploaded file so you can retry without uploading again.
- After a successful submission, check the current package or pending status in package records. Once published, reopen the distribution link and verify that platform's version.
Results of each release mode
| Mode | Result after submission | Next step |
|---|---|---|
| Publish now | The new package becomes the current version | Check the version on the download page and the actual package |
| Save prerelease | Keeps a pending package without replacing the current version | Confirm publication from the pending record |
| Schedule release | Saves a pending package and release time | Check the result when due; review the existing plan before changing it |
Why the old version remains after upload
Save prerelease only retains a candidate; scheduled releases continue serving the old package until the scheduled time. Check Version releases in app details. To publish manually, select Publish now on the pending version and confirm.
If Release incomplete or Awaiting reconfirmation appears, read the record's message before retrying. Use Review and reconfirm for a current-version conflict. Upload completion is not publication success.
Check the current Android and iOS versions separately, then download and inspect each package on the target device. Sharing a download page does not update both platforms at once. Downloads already started keep the old version; new downloads use the published version.
When an update is blocked
States such as an app being taken down may block package uploads or replacements. Resolve the app status first. For a package-name mismatch, check that you selected the correct app; do not change file extensions to bypass validation.
Keep the error and file version after an upload failure. If a release plan exists, review it before retrying to avoid duplicate replacements.
Package scope
Main package replacement differs from special download settings. ZIP files, profiles, PC files or existing URLs in special settings do not automatically replace the current Android or iOS main package.