Archiving a release removes its build file and hides it from install links, while preserving all comments and activity history. This article explains what archiving does, how to archive releases manually or in bulk, and how to configure automatic archiving.
What Archiving Does
When you archive a release, the following happens:
- The build file (.apk / .ipa) is permanently deleted — it cannot be recovered
- The release is hidden from install links and removed from the app
- Any tasks linked to the release are unlinked
- All comments, conversations, and activity history are preserved
- The release no longer counts toward your team's storage quota
Archiving is irreversible. There is no unarchive option for releases. If you need the build file again, you must re-upload the release.
How to Archive a Release
Archive a Single Release
- Open the release from the releases list or the release detail page
- Click the three-dot menu (⋯)
- Select Archive Release
- Confirm in the dialog
Bulk Archive
- In the releases list, select multiple releases using the checkboxes
- Click Archive in the bulk action toolbar that appears
- Confirm in the dialog
Archive on Upload
When uploading a new release, you can choose to automatically archive the current latest release once the new upload completes. This option appears during the upload flow.
Auto-Archive Settings
TestApp.io can automatically archive releases after a set period of time. To configure this:
- Go to App Settings for the relevant app
- Find the Auto Archive section
- Choose a time period (for example, 30 days or 3 months) after which releases are archived automatically
- Set it to Never to disable auto-archive for that app
There are two levels of auto-archive configuration: a team-wide default and a per-app override. The per-app setting takes priority over the team-wide setting.
Archive vs. Delete
Both archiving and deleting a release free up storage and remove the build file. The key difference is what happens to the release record itself:
| Archive | Delete | |
|---|---|---|
| Build file (.apk / .ipa) | Removed | Removed |
| Release record | Kept | Removed |
| Comments and history | Preserved | Removed |
| Storage quota freed | Yes | Yes |
| Reversible? | No | No |
Use archiving when you want to retain the release history for reference but no longer need the build file. Use deletion when you want to remove the release entirely.
Archiving App Projects
Archiving an individual release is different from archiving an entire app project. App-level archiving hides the app from your dashboard but can be reversed — you can unarchive an app at any time from its settings. Release-level archiving is permanent and cannot be undone.
Related Articles
Need help? Contact us — we're happy to assist!