Known issues
Current, customer-visible limits.
Updated 24 August 2026
- The iPhone and iPad app is not publicly distributed yet.
- The macOS beta is authenticated by Fold's updater signature but is not Apple-notarized. After dragging Fold to Applications, approve its first launch in System Settings โ Privacy & Security โ Open Anyway.
- Intel macOS, Windows ARM, Linux ARM, Android, and browser clients are unavailable.
- The Debian package does not self-update; download the next signed DEB manually.
- Windows voice calls remain gated where the native audio backend cannot meet the shipped device contract.
- Fold does not use raw APNs or PushKit device tokens until the metadata and notification-privacy architecture is approved; iOS background delivery is therefore best effort.
- Fold ships no remote AI provider. On-device memory works locally; a remote reader is an explicit future integration.
- Independent key-transparency witnesses are not operated yet; same-size split-view evidence relies on client gossip.
- Right-to-left desktop message layout and the full physical accessibility matrix still need native-device verification.
- Six upstream RustSec advisories remain in the stable OpenMLS/libcrux dependency line; Fold enforces the non-vulnerable algorithm paths and adds input hardening, but cannot truthfully call the upstream graph advisory-free.
For a defect not listed here, use support. For a vulnerability, report it privately.