FOLDPAIR / RELEASE 0.2.563
Foldpair 0.2.563
Get the update.
Get Foldpair 0.2.563 for your devices.
Download FoldpairChoose a platform · Version 0.2.563
- Windows
- macOS · Apple Silicon
- macOS · Intel
- Linux · x64
- Linux · ARM64
- Android
- iPhone / iPadNot available for this release
WHAT’S NEW
A quick look at this update
Foldpair 0.2.563 packages the latest documented beta improvements across relay resilience, network fallback, storage, and encrypted sync.
Full release notes
Highlights
- Your transfer list now says what became of each file you sent.
Transfers now distinguishes delivered, declined, withdrawn, waiting and expired offers. Previously, all of them appeared as sent, so a declined file looked the same as one that arrived.
- Taking a file back no longer tells the other person it "expired".
Withdrawing an offer was recorded as an expiry, so someone pressing Accept a moment too late was told they had been too slow, when in fact the sender had changed their mind. The two are now different events with different words.
- Transfers use the name you gave a contact.
A row could show a raw account id for somebody your Contacts page names perfectly well, because it used the name that person set for themselves rather than the one you chose for them.
- Send-to-a-contact no longer disappears until you restart the app.
Send-to-contact availability is now remembered separately for each relay. A refusal from an older relay or a temporarily disabled deployment no longer hides the feature after you switch to a relay that supports it.
- An invitation emailed to an address can no longer get stuck retrying.
An emailed folder invitation whose owner is unavailable now waits longer between attempts. It no longer repeats the same unsuccessful claim and contact updates every 30 seconds throughout the invitation’s lifetime.
- Re-adding a contact can no longer quietly undo a block.
Re-adding a contact can no longer quietly undo a block.
Fixes
- Transfers now distinguishes delivered, declined, withdrawn, waiting and expired offers. Previously, all of them appeared as sent, so a declined file looked the same as one that arrived.
- Taking a file back no longer tells the other person it "expired". Withdrawing an offer was recorded as an expiry, so someone pressing Accept a moment too late was told they had been too slow, when in fact the sender had changed their mind. The two are now different events with different words.
- Transfers use the name you gave a contact. A row could show a raw account id for somebody your Contacts page names perfectly well, because it used the name that person set for themselves rather than the one you chose for them.
- Send-to-contact availability is now remembered separately for each relay. A refusal from an older relay or a temporarily disabled deployment no longer hides the feature after you switch to a relay that supports it.
- An emailed folder invitation whose owner is unavailable now waits longer between attempts. It no longer repeats the same unsuccessful claim and contact updates every 30 seconds throughout the invitation’s lifetime.
- Re-adding a contact can no longer quietly undo a block.
- You can send a file to a contact as well as to your own devices. The contact receives an offer and one of their devices downloads it into Received after acceptance. You can withdraw it until it is claimed and see whether it is waiting, accepted, declined or expired. When contact sends were first introduced, they used encryption in transit and at rest but did not yet use end-to-end encryption; synced folders provided that protection at the time. Neither person sees the other’s device details. The relay operator enables contact sends per deployment.
- The encryption table gained an entry for one-off device sends. At the time of that change, these sends did not yet use end-to-end encryption, unlike synced folders, clipboard items and new browser share links.
- Accepting a shared folder now proposes an incoming folder, Foldpair Incoming/<folder name>, and shows its path before downloading. Choose Change location… to use another folder. Not now leaves the invitation pending in Contacts; cancelling the location picker returns to this choice.
- People who join an encrypted folder through Contacts or an emailed invitation can now receive its key. Previously, only an invitation link carried the key, so other accepted members could not decrypt the files. The owner’s app now encrypts a copy of the key for each accepted member who needs it; the relay cannot decrypt that copy.
- Folder invitations sent to an email address now appear after the recipient installs Foldpair and verifies that address. An invitation received later appears on the next refresh. The recipient must still accept it before gaining access. This applies to folder invitations, not links for adding an account device.
- Invitation emails and the join page now tell new recipients to install Foldpair and sign in with the invited email address. The installer does not preserve the invitation link, so the instructions no longer rely on it surviving installation.
- Windows Setup can continue when it cannot verify a legacy-updater cleanup step through WMI or Task Scheduler. It still attempts to stop and remove the old updater, but logs an unverified cleanup step instead of sending the user into an ineffective restart-and-retry loop.
- Beta upgrades can use the Paddle Sandbox checkout. Beta testers can open the official foldpair.com checkout when the relay explicitly reports Sandbox mode. Their verified-email accounts and plan access persist, while the Paddle payment uses test money. Temporary tunnel checkout URLs remain limited to local test relays.
- Fresh Windows installs no longer fail a legacy-updater check. Setup now treats an absent legacy scheduled task as the normal state without depending on a version-specific Task Scheduler error identifier. A detected enabled legacy task or a still-running updater continues to block installation.
- Windows upgrades no longer fail on harmless legacy cleanup leftovers. Setup checks only the named legacy scheduled task instead of enumerating every task on the machine, accepts a task that is already disabled, and treats a locked obsolete LocalAppData application tree as recoverable after proving that no legacy updater is running. An active updater or enabled legacy task still blocks the upgrade.
- Mirror downloads remain readable after activation. The publisher sets their read permissions before moving them into the web server’s download directory, preventing HTTP 403 errors caused by a restrictive SSH file-creation mask.
- Windows setup now retries transient legacy-tree file locks. After stopping the obsolete updater, both Setup and the one-line installer retry removal of its LocalAppData application tree for up to 15 seconds. A short-lived archive or process handle can no longer turn a successful updater shutdown into an immediate restart-required installation failure.
- RecruitLead download instructions no longer depend on the primary domain. Pages reached through the CIS mirror now show mirror-hosted one-line installer URLs, and /get.ps1 plus /get.sh default their release-feed requests to that same mirror ingress and use the mirror artifact URL returned by the feed. Mirror deployment and release verification reject either script if it contains a primary-domain dependency.
- Windows upgrades now retire even an already-running legacy beta updater. Setup disables and removes the old scheduled task, terminates its active PowerShell/VBS process tree, verifies the scheduled task is absent or disabled, and makes a best-effort removal of the obsolete LocalAppData application copy. This closes the race that could restore and launch an old beta one second after a successful Program Files installation while preserving settings and synced folders.
- Windows one-line upgrades now complete cleanly over running beta clients. The PowerShell flow downloads a recognisably named installer, closes existing launcher and agent processes, waits for setup to finish, verifies the installed binary version, and explicitly opens the matching launcher from Program Files. The release packager also rejects stale launcher or agent payloads whose FileVersion does not match the installer version, so a current filename cannot conceal old application bytes.
- One-command Windows upgrades handle running beta clients. The PowerShell flow downloads a clearly named installer, closes running launcher and agent processes, waits for Setup, checks the installed version, and opens its launcher from Program Files. Packaging also checks launcher and agent FileVersion values against the installer version to help catch stale components.
- Folder and account contention can be isolated. The optional sharded lock manager separates write contention by folder and account. A fair-share throttle slows an overactive account, and per-account lock metrics are available on /metrics. These controls reduce the risk that one account delays the rest of the service.
- PostgreSQL is now a supported metadata backend for the relay (selectable by configuration), alongside the existing SQLite store which remains the default for local and self-hosted use. Includes a one-shot SQLite→Postgres data migration tool with row-count reconciliation.
- Support for Cloudflare R2 and S3-compatible blob storage. The relay can store encrypted blobs in R2 and provide presigned downloads. Storage health checks and a global storage cap help detect failures and limit usage. The integration was tested with an S3 server.
- Storage maintenance can run after startup. The startup storage audit can run after the server begins listening, allowing health checks to respond while storage cleanup continues. FOLDPAIR_STARTUP_AUDIT_MODE selects background (the default), off, or blocking for the earlier pre-listen behaviour.
- End-to-end encryption for synced folders and clipboard. File contents are encrypted on the sending device with AES-256-GCM in authenticated frames before upload. Folder keys are delivered to devices in sealed ECDH envelopes; the relay has no unwrapped content keys. Clipboard items are encrypted per event with the account key. For these protected payloads, the relay stores ciphertext without a decryption path. Uploads wait if a participating device does not yet support E2E, so update every device in the folder before transfers resume. Clipboard E2E has been enabled by default since 2026-06-15.
- Remote file access hardened alongside folder encryption.
Known issues (1)
Known issues
- macOS beta packages are unsigned and not notarized; follow the documented Gatekeeper first-launch steps.
Checksums and verification
- Windows
d13154c37f95e185d17bcb2e968a36eb48c3e5a84c6e102dee6f258065084537 - macOS · Apple Silicon
644c2a782ecc6cb0ae9d4f23bb4e69b4e544e99587e607272e3fca9b114d67e1 - macOS · Intel
f5edd546f95f0d29a1c4dfbd99b2f5379d310db047207bf82bfa6beb63c8c6eb - Linux · x64
579004d677eba3ea02e8eb4df5b41f43f6b19de7fc7c554d6c5ced7be7fea601 - Linux · ARM64
0968c5c1224a7757a147b5c8df35210f358c0e6e32503b5a0841084df79ba0ef - Android
b9a94fd196b330f583e55b66d379a37f17d34021b37f93346b5e9f3bbee61230
GET THE UPDATE
Update your other devices.
Download Foldpair 0.2.563 for each of your devices.
Download FoldpairChoose a platform · Version 0.2.563
- Windows
- macOS · Apple Silicon
- macOS · Intel
- Linux · x64
- Linux · ARM64
- Android
- iPhone / iPadNot available for this release