Known Limitations and Release Gates

Known Limitations and Release Gates

This page distinguishes a source-complete feature from a released, supported product.

Distribution

• No prebuilt signed application is published.
• The app is not notarized.
• No App Store package or listing exists.
• Update delivery is not implemented.
• The permanent application icon is deferred.

Platform

• macOS 26 or later is the configured deployment target.
• Xcode 27 or later is the documented build environment.
• Apple silicon is the automated validation target.
• The TDLib artifact includes x86_64, but Intel app execution is not a current release gate and is not claimed as validated.

Telegram behavior

• Complete-history duration depends on chat size, network conditions, Telegram availability, and service limits.
• Telegram may omit the original filename for some media. In that case Unspool uses a visibly generated neutral fallback.
• Future TDLib authorization states can appear as unsupported until mapped.
• Cached summaries and scans can be stale until refreshed.
• Local download history is not a checksum-based content database.

Filesystem behavior

• Save a Copy intentionally changes the destination name after explicit user choice.
• Destination bookmarks can become stale when folders or volumes move.
• File size is validated when Telegram supplied an expected size; content hash verification is not currently part of placement.
• Unspool does not scan downloads for malware.

Manual release acceptance

Before a first public binary, verify on a clean Mac account:

1. fresh Telegram API setup;
2. login by phone and current code;
3. two-step verification;
4. Switch Account and Sign Out semantics;
5. main and archive chat ordering;
6. fast 25-message scan and exhaustive multi-page scan;
7. FLAC sent as Telegram music with exact original filename;
8. document, voice, video, animation, image, sticker, LRC, and unfamiliar extension mapping;
9. long Unicode and edge-case filenames;
10. cross-chat isolation during slow scans;
11. one and six concurrent transfers;
12. pause, resume, cancel, retry, and relaunch recovery;
13. insufficient disk space;
14. stale or unavailable destination bookmark;
15. Skip, Replace, and Save a Copy with real existing files;
16. network loss during scan and download;
17. Finder reveal;
18. VoiceOver and full keyboard operation;
19. Reduce Motion, Reduce Transparency, and Increase Contrast;
20. System, Light, and Dark appearances.

Release engineering still required

A distributable release also needs:

• final application identity and icon assets;
• signing identity and hardened-runtime review;
• notarization;
• release archive validation;
• an update and rollback policy;
• versioned changelog and supported-version policy;
• final privacy, terms, and dependency review for the distribution channel.