Skip to main content

​
How often

Frequently. Several builds a week is normal during active development, each usually a small fix or a new screen.

​
The easy way

Turn on Automatic Updates in TestFlight, once:
1

Open TestFlight

2

Tap VT Workbench

3

Turn on Automatic Updates

From then on, new builds install themselves and you can stop reading this page.

​
The manual way

Open TestFlight. If a build is waiting, the button says Update. Tap it.

​
Should you skip updates?

Please do not. Fixes often depend on each other, and a tester several versions behind reports bugs we fixed a fortnight ago — which costs us time and gains you nothing. If you have been away and there are several updates, just take the newest; they are cumulative.
Your data survives updates. An update is not a reinstall — everything stays exactly where it was. The only situation where data is at risk is deleting the app entirely, which is what Backup and restore is for.

​
What is in each build

TestFlight shows What to Test notes on each build, which we use to say what changed and what is worth poking at. If a build introduces something we specifically want eyes on, that is where it will say so.

​
If an update breaks something

Tell us immediately, and mention which build number you are on — TestFlight shows it beneath the app name, and the Workbench shows it at the bottom of the side menu. A bug report that names the build is far more useful than one that does not, because it tells us exactly which change to look at.