Expand items by topic to read validation records and planned work.
Device discovery and trust
Device discovery and trust · Tested subset
Discover devices, verify identities and establish trusted connections.
Development builds · 11–12 Sep 2026 · SDK tests on physical devices and UI regression tests
Completed validation
- All three local-network pairings between Android, iOS and macOS completed discovery and security-code confirmation on both ends.
- Device names, local labels and duplicate discovery entries have dedicated regression coverage.
Current limitations: This stage summarizes the scope verified for its child nodes. It does not certify every device model or complete user workflow.
Next steps: Validate first-time pairing with more routers and system permission states.
Local-network discovery · Tested subset
Find devices available for pairing on the same local network.
Development builds · 11–12 Sep 2026 · Three-platform device tests and regression tests
Completed validation
- A Mac, Pixel 7 Pro and iPhone SE discovered and connected to one another on the same Wi-Fi network.
- Regression tests cover merging duplicate entries for authenticated devices, recovery windows and retaining newly discovered devices.
Current limitations: Network isolation and app network permissions can affect discovery. Finding a device does not establish trust.
Next steps: Test more routers and permission-denial followed by reauthorization.
Security codes and pairing · Tested subset
When pairing a new device, verify the security code and confirm on both ends.
Development builds · 11–12 Sep 2026 · LAN and relay diagnostic experiments; the relay experiment is not part of the RC1 installers.
Completed validation
- The three LAN pairings and a cellular relay experiment completed matching security codes and confirmation on both devices; the relay experiment is not part of the RC1 installers.
- Pairing packet-loss and early-confirmation scenarios passed regression checks.
Current limitations: Device names do not establish trust. The relay experiment is not part of the RC1 installers.
Device names and local labels · Tested subset
Set a device name and add labels for paired devices that are visible only on your device.
Development builds · 12 Sep 2026 · SDK and UI regression tests, plus selected Android interactions
Completed validation
- SDK tests verified that renaming preserves identity and relationships, and updates the name on the peer after reconnection.
- UI tests cover editing and clearing labels and handling failed saves. The Android client entry points were checked.
Current limitations: Name and label editing on iOS has not been manually validated step by step. Labels only affect local display.
Files and messages
Files and messages · Tested subset
Exchange messages, images and files in a device conversation.
Development builds · 11–12 Sep 2026 · Three-platform SDK tests and selected client workflows
Completed validation
- Bidirectional messages and file integrity checks passed for all three local-network platform pairings.
- In-conversation file controls, image cards and input interactions have regression coverage and manual experience checks.
Current limitations: SDK transport tests and complete client workflows are validated separately. System file selection, saving and background transfers still have cases to cover.
Next steps: Cover remaining ordinary-product file selection, saving and background workflows.
Messages and images · Tested subset
Send text and images, and browse conversation history on your device.
Development builds · 11–12 Sep 2026 · Three-platform SDK messaging and selected client image workflows
Completed validation
- Bidirectional messaging passed for every pairing of the three platforms on a local network.
- A Pixel sent an image to a Mac with matching content checks; its history entry was not duplicated after restart.
Current limitations: The image workflow above covers Pixel → Mac. The iOS photo-library entry point has not been validated step by step.
Next steps: For the next candidate, focus on the P20 image picker, Pixel comparison, iPhone photo permissions and send confirmation. The reported image-picker exit is not yet closed at root-cause level.
File transfers · Tested subset
Select files in a conversation, view progress and receive files.
Development builds · 11 Sep 2026 · Same Wi-Fi network, product SDK in separate test apps
Completed validation
- Mac ↔ Pixel, Mac ↔ iPhone and Pixel ↔ iPhone each completed a 32 MiB file transfer in both directions.
- Independent SHA-256 checks matched for the actual received files in all six transfers.
Current limitations: This experiment does not replace full-client acceptance testing for file selection, external saving, background resumption or restart recovery. It is not a transfer-speed promise.
Next steps: Retest image and file selection, receipt, opening and interruptions on each platform using the next candidate package.
Cross-platform validation · Tested subset
Android, iOS, macOS and Windows have interoperability records for specified device combinations.
Isolated development packages · 11–26 Sep 2026 · specified device pairs in each run
Completed validation
- All three pairings completed discovery, security codes, bidirectional messages and bidirectional file verification.
- Each device held two online sessions at once; the data paths were confirmed to use Wi-Fi.
- 26 Sep: Windows ↔ Mac passed re-pairing, bidirectional text and file-integrity checks, rejection/cancellation and original-task recovery.
Current limitations: Isolated-host checks do not certify the native UI of public installers or every platform pairing. iOS is not publicly available.
Next steps: Expand device coverage and complete remaining ordinary-product workflows.
Bluetooth short messages · Tested subset
Exchange authenticated short text and delivery receipts between nearby devices over Bluetooth.
Isolated development packages · 16–30 Sep 2026 · dated nearby device pairs
Completed validation
- Messages and receipts were checked in all six directions with only Bluetooth available to the phones.
- Over-limit requests were rejected, and subsequent normal messages still worked.
- 26 Sep: Windows ↔ Mac passed both scan/advertise roles and bidirectional short text. 30 Sep: Pixel ↔ iPhone SE and Pixel ↔ P20 passed both roles, short text and receipts.
Current limitations: No file transfer or guaranteed background delivery. Intermittent one-way discovery was reported for P20/Pixel. P20 acceptance was not completed, and this issue is not claimed as fixed.
Next steps: Complete role combinations, recovery and product-workflow checks for the nearby candidate.
Validation and distribution
Validation and distribution · To do
0.1.1 (16) provides Android, macOS and Windows downloads. iOS 0.1.0 (15) still awaits export compliance.
Planned work
- Address installation and usage feedback for the released packages.
- Complete iOS export compliance and final store-build verification before submitting for review.
- Record further developer-tool validation separately from client releases.
Current limitations: This release provides only Android, macOS and Windows clients. It adds no iOS, Linux or SDK downloads. Folder transfer, cross-network connections and relays are outside this release.
Network compatibility · To do
Broaden validation of local-network configurations and permission states.
Planned work
- Test more home Wi-Fi networks, hotspots and router configurations.
- Record recovery after permission denial, network isolation and discovery-failure states separately.
Current limitations: This work covers nearby communication, not cross-network direct connections or relay acceptance.
Network and interruption recovery · Tested subset
Validate interrupted-file resumption and automatic recovery when phones return to the foreground.
Isolated development packages · 16–26 Sep 2026 · Mac/Pixel/iPhone and Windows ↔ Mac
Completed validation
- File tasks resumed automatically after process interruption, retained their original task IDs and passed integrity checks.
- Bidirectional Pixel-to-Mac/iPhone files resumed after Wi-Fi interruptions and passed checksum checks.
- After 30-second, 2-minute and 10-minute locks, iPhone recovered automatically with queued messages and original contacts retained.
- 26 Sep: after terminating the receiving process in each Windows ↔ Mac direction, restarting completed the original approximately 128 MiB transfer with matching SHA-256.
Current limitations: File-recovery stress checks used isolated hosts with the RC1 SDK. Lock recovery is a separately recorded tested subset. The RC1 client passed upgrade and send/receive smoke checks only; more devices, background conditions and Mac sleep remain untested.
Next steps: Complete the remaining cases against explicitly identified devices and release builds.
Installation, upgrades and release · Tested subset
0.1.1 improves image drafts, Android rendering compatibility and Bluetooth status messages. Earlier validation records remain version-specific.
0.1.1 (16) · 30 Sep 2026; validation records are retained by version below
Completed validation
- Release packages, 30 Sep: versions and download digests were checked for all three 0.1.1 (16) packages. Android retains its release signature, macOS is signed and notarized, and Windows is unsigned.
- Historical RC1: Final signed packages retained existing contacts and chat history after upgrades on all three devices.
- Historical RC1: Final-product messages and receipts passed Mac → Pixel → iPhone → Mac; a Chinese-named file was received and opened on Pixel from Mac.
- Historical RC1: Android uses the release key; macOS uses Developer ID signing and Apple notarization; iOS uses private Ad Hoc distribution to registered devices.
- Historical RC1: 17 Sep 2026: Windows x64 ZIP and notarized macOS DMG added. Windows native build, package integrity and DLL loading checked; the macOS application is unchanged from RC1.
- Historical RC1: A user reports working operation on a Huawei P20 and an HONOR smart screen. OS versions and the screen model remain unrecorded. This is user feedback, separate from automated acceptance evidence.
- Release packages, 27 Sep: public downloads for all three platforms were checked against their digests. Android release signing and macOS Developer ID signing/notarization passed. The Windows portable package is not code-signed.
Current limitations: Full acceptance was not completed for this release. Historical and isolated-build records do not establish complete validation. P20 acceptance is incomplete, and its reported issues are not claimed as fixed. No public iOS download is available.
Next steps: Record further issues and fixes by platform and release. Isolated acceptance builds do not establish complete validation of release packages.
iOS App Store preparation · To do
iOS/iPadOS 0.1.0 (15) has been uploaded to App Store Connect and store information has been saved. It has not been submitted for review or released.
27 Sep 2026 · iOS/iPadOS 0.1.0 (15)
Planned work
- Complete export-compliance classification and required documentation based on the actual encryption implementation.
- After compliance is resolved, complete internal verification of final store build 15, then submit for review.
Current limitations: Simulator and isolated test builds do not replace acceptance of store build 15. There is no public iOS download; no review outcome or release date is promised.
DevTools platform validation · Tested subset
macOS arm64 and Windows x64 builds, UI and local two-process communication have passed.
17 Sep 2026 · macOS arm64 Release / Windows x64 MSVC Debug · SDK 0.1.0 / ABI 25
Completed validation
- Both hosts passed SDK loading, Unicode paths, pairing, bidirectional delivery receipts and file integrity checks locally.
- GUI self-checks, identity reopening and wrong-password protection passed; source and validation records are committed in the DevTools repository.
Planned work
- Add cross-device LAN, Windows high-DPI and manual debugging checks.
- Validate native Linux builds before deciding its packaging requirements.
Current limitations: Communication checks used two processes on each host, not cross-device networking or desktop BLE radios. These checks used the corrected development SDK; RC1 client packages were not replaced.
Zhiyu