Build Versioning and Revision History on AppForShare
By Zakir Umair · · 4 min read
AppForShare keeps a history of your app builds through projects: each app is a project, and every upload becomes a new build in that project with its own install link, version number and (on Pro and Team) release notes. Uploading a new version never overwrites the previous one, so testers can still install an older build from its link while that link is live. AppForShare does not compare files or show differences between builds, and it does not roll back apps already installed on a device.
This post explains how build history works, how to go back to an earlier build, and how long old builds stay available.
What versioning means for app builds
In document tools, versioning means keeping earlier copies of a file so you can undo a mistake. For mobile app testing, the need is similar but more specific:
- Testers need to know which build they have and what changed in it.
- QA sometimes needs to reinstall an earlier build to check whether a bug is new.
- Clients may want to compare the current build with the one they approved last week.
The source of truth for code history is still your version control system, such as Git. AppForShare keeps the built binaries that testers install.
How AppForShare organizes builds
| Concept | What it is |
|---|---|
| Project | One app, grouping all its builds |
| Build | One uploaded APK or IPA, with its own install link and QR code |
| Version | The version and build number read from the app file |
| Release notes | Text you attach to a build to explain what changed (Pro and Team) |
Because each build has its own link, sending a new build never changes what an old link installs. Links are never reused, so an old link or QR code will not start pointing to a different build.
Release notes as revision history
On Pro and Team you can attach release notes to each build, either in the dashboard or from CI with the --notes or --notes-file option of the AppForShare CLI. A common pattern is to use the commit message or a changelog entry. Over time, the notes on each build form a readable history of what testers received and when. See uploading builds from CI.
Installing an earlier build
To go back to an older version:
- Open the project in the dashboard and find the earlier build.
- Share its install link or QR code with the tester.
- The tester installs it on the device.
Keep in mind how mobile operating systems treat downgrades:
- Android normally refuses to install an APK with a lower version code over a newer one. The tester uninstalls the app first, which deletes its local data.
- iOS may allow installing an older build over a newer one, but local data written by the newer version may not be compatible. Uninstalling first is the safest route.
AppForShare does not push older versions to devices automatically. There is no remote rollback.
How long old builds stay available
| Plan | Link life | Storage |
|---|---|---|
| Guest | 3 days | n/a |
| Free | 7 days | 2 GB |
| Pro | While subscribed | 25 GB |
| Team | While subscribed | 150 GB |
On Pro and Team, older builds stay installable while the subscription is active and you have storage space. If you delete a build by mistake, you can restore it for 7 days. After that the file is removed for good. For more, read how long links stay available.
What AppForShare does not do
- It does not show differences between two builds or their files.
- It does not replace version control for your source code.
- It does not roll back apps already installed on testers' devices.
- It does not keep deleted builds beyond the 7-day restore window.
Practical tips
- Increase the build number on every upload so testers and analytics can tell builds apart.
- Write release notes that say what to test, not only what changed.
- Delete builds you will never need again to save storage.
- Keep the build you shipped to the store in your own archive as well.
Frequently asked questions
Does uploading a new build replace the old one?
No. Every upload becomes a new build in the project with its own install link. Earlier builds and their links stay as they were.
Can I roll back to an earlier version of my app?
You can share the install link of an earlier build if it is still live, and testers install it themselves. AppForShare does not roll back apps that are already installed on devices.
Does AppForShare show what changed between builds?
Not automatically. On Pro and Team you can attach release notes to each build to describe the changes. AppForShare does not compare files or show diffs.
Can I recover a deleted build?
Yes, for 7 days after deletion. After that, the file is removed permanently.
