Managing versions

Studio's version control feature lets you thoroughly test any changes before you release them to your end users.

However, there is always a chance that a bug is only discovered after it is released. If it does, you will often want to roll back to a previous version until the problem has been resolved.

Rather than reverting your project and creating a new release in Studio, Ease Live lets you change the public version in seconds.

Changing the public version

To change your project's public version, open a project and find the version picker below the header bar - if you haven't changed it before, it will say "Latest version":

Note that you will only see releases here – snapshots are not eligible. The default and recommended setting is "Latest release", so you don't have to update this for every release under normal circumstances. To pick a different release, simply select it in the list and click "Save...".

New vs active sessions

When you change the public version, you can decide whether to apply it to just new sessions, or active ones as well.

New sessions only means that people who have already loaded your UI will not be interrupted, and still see the version that was selected when they joined.

Active sessions are users that have already loaded your UI. This option will force the overlays to automatically refresh, loading the new version. This is often a good idea for critical bugs, but it will interrupt the experience for anyone who was interacting with the overlays at the precise moment you changed the public version.

Reminder

Make sure to set version back to default (latest published) once issues are resolved, to ensure that users continue to get the latest updates.

Speficying the version in the URL

In your project settings, you can modify the web app URL served to your production, development and staging environments separately (as requested via the Ease Live SDK). It is possible to specify the project version here, by adding a &version=<number> URL parameter.

This will override your public version setting. The accepted parameters are:

• A version number: Any version number from your version list in Studio
• latest: This will serve the newest published release
• draft: Show the project as it is right now in Studio

Careful

Ease Live will always respect the version explicitly set in the URL, even if it is a snapshot. You are strongly encouraged to only set the version manually for your development/staging environments. For production you should always select the public version via the menu.