What changed since 1.0.2?
- In 1.0.2, a network reset could stall during an outage or network change and block telemetry and control requests. In 1.0.3, resets run on a separate queue with a three-second wait budget. Recovery then continues with network settings restoration, while only one reset remains in flight.
- In 1.0.2, a provider terminated by the system could be treated as a normal disconnect, leaving the user to reconnect manually. In 1.0.3, unexpected exits are detected and retried while the user still wants a connection. Up to five retries use delays of 1, 3, 8, 20, and 45 seconds.
- Connection intent is now tracked separately. Disconnect cancels pending retries; a manual connection or successful recovery resets the retry budget.
Validation coverage
- 485 unit tests passed. Developer ID signatures, app and DMG notarization, and stapled tickets were verified.
- Tart macOS 26.6.1 checks covered upgrading from 1.0.2, TUN recovery after 20/60-second outages, reconnects after both providers exited unexpectedly, and remaining disconnected after a user stop.
Known limitations
- HTTPS to ipv6.google.com failed with the test configuration and also failed after rollback to 1.0.2. Requests to regular Google, Cloudflare, and Baidu succeeded. Native IPv6 remains unverified.
- The first recovery took about 48 seconds, including about 45 seconds of delayed status processing. Later TUN and transparent proxy recoveries took about 8 and 7 seconds.
- The original hotspot-switch hang was not reproduced. Actual system sleep/wake, the full protocol matrix, and a 24-hour stability run were not completed.
Requirements
- Apple silicon · macOS 15.0+
Download and verify
AetherRoute-1.0.3-build-2026091402-arm64-Notarized-Test-Normal-Core.dmg
SHA-256
8c718673f4c352069a15a220db79b67cf03feda1d1dd414cf8151a14b9aad016
After downloading, run this in Terminal and confirm the output matches:shasum -a 256 ~/Downloads/AetherRoute-1.0.3-build-2026091402-arm64-Notarized-Test-Normal-Core.dmg