Signed updates
Short answer: Every update package is cryptographically signed and verified on your machine before it installs; an update that doesn’t verify is rejected, full stop.
How does update verification work?
Build Perch checks for updates in the background and, when one’s available, downloads the update package from a single fixed feed the app trusts. Before installing anything, it verifies the package’s signature against a public key that ships baked into the app itself. If the signature doesn’t check out (a corrupted download, a tampered file, anything served from somewhere other than the real feed), the update is rejected and nothing installs. Update checks and installs never read or carry your content; they only exchange the update package itself.
Do I need to configure anything?
No. There’s nothing to configure. Update checks happen automatically in the background; when a signed update is ready, the app offers to install it.
Good to know
- A license past its update window (see Trial, licensing & devices) sees a “Renew” prompt instead of an install button; the verification step is the same either way, it’s just gated by whether your license currently includes updates.
- Signature verification happens locally on your machine; it doesn’t require or use a network call beyond fetching the package itself.