Files and update builds

Open an app and choose Files. You need the Files permission.

Files

Upload a file (up to 25 MB) and, optionally, limit it to tiers. A signed-in client asks for it by ID (file_…):

1. The server checks the user’s tiers and answers with the file’s size, SHA-256 and a download link signed with the app’s key. The link expires after 2 minutes.
2. The SDK downloads it and checks the size and SHA-256 before your code sees the bytes.

Like variables, a file the user can’t access and a file that doesn’t exist both return FILE_NOT_FOUND. Mark a file Free users to also offer it to free mode devices.

You can rename a file, change its tiers, or delete it. Storage counts toward your plan.

Update builds

In App settings → Client rules, Update build lets you upload your installer or .exe (up to 95 MB). Clients are then sent a signed link to it, with its SHA-256, size and file name:

• in the UPDATE_REQUIRED answer, when their version is below your minimum, and
• in the optional “update available” info on sign-in and heartbeats.

The link is absolute (it is opened in a browser), stays the same for an hour and expires on the hour after next. You can also pick any file from Files with Use as the update download.

The external download URL is only a fallback, used when no build is set. Replacing an upload deletes the old one; deleting the update file falls back to the URL.