Skip to navigation

Updates and release channels

Open Updates in your app’s sidebar. Each channel has its own latest version, download link and release notes.

ChannelLatest versionDownload link
Stable1.4.0https://example.com/ger-1.4.0.zip
Beta1.5.0-beta.2https://example.com/ger-beta.zip

Set up your releases

  1. Open Stable and enter the version and download link you want most customers to use.
  2. Add Beta if you want a separate test release. Enter its version and download link.
  3. Open the Settings tab and turn on Check for updates.
  4. Choose the default channel for new identities. Existing assignments stay unchanged.

Your previous automatic-update link is kept in Stable. Stable cannot be deleted.

Choose who gets Beta

Open a user, license or standalone device and choose its Release channel. Select several records and use Change channel to update them together.

A plan can set a default channel for new identities. Changing the plan default does not move identities you already created. A linked username and license share one assignment; device activations use their user’s or license’s assignment.

What the API returns

Initialization has no signed-in identity, so it returns update.requiresLogin: true without a personal download link. The login response and successful session checks return the assigned release under data.update, with channel, channelName, version, url and notes. data.updateAvailable tells the client whether a newer release is offered.

Changing a channel does not install anything. Semantic version comparisons avoid offering an older release as a new update. Use versions such as 1.4.0 and 1.5.0-beta.2; custom version labels are compared as different labels.

Allowed Versions is separate

Allowed Versions controls which builds may connect. Channels control which update a customer receives. Assigning Beta does not stop that customer running an allowed Stable version.

A verified sign-in blocked by Allowed Versions returns UPDATE_REQUIRED with the assigned update details, without issuing a session. An existing session blocked by a version change receives update details too.

A MediaFire page should open in the browser. A direct ZIP or installer link can also be opened in the browser. AuthlyX currently provides release information; it does not silently install files or close the customer’s application.

SDK-specific update screens and download helpers are a separate integration step. Direct API users can read the fields above immediately.