Retry Times starts again after a good connection

Checks that Retry Times counts failures in a row, so a profile that keeps reconnecting successfully does not run out of attempts.

VERIFIED — TESTED SUCCESSFULLY  Tested on 10 November 2026 on the current app build against WaterWall 1.5.42, the official release, unchanged.

Result

OutcomePassed: every check succeeded.
Test length16 seconds, including connecting and disconnecting

What the test does

  1. The profile uses Auto Reconnect on and Retry Times 1.
  2. The test connects and makes WaterWall inside the app stop; the connection must come back within 30 seconds.
  3. It makes WaterWall stop a second time; the connection must come back again.

Passes when the connection comes back both times. With a count that never started again, the second failure would end the VPN.

Test setup

The profile used the chain of the VLESS + TLS scenario, with the same server copy and profile settings, except the options the steps above change.

PhoneiPhone 12 with iOS 27.2 (build 24B119), on Wi-Fi
AppSRP VPN Connect 1.2.0 (build 41), a Debug build of commit e69cb668, installed by Xcode for the test. TestFlight build 41 is commit e44cf11d, with the same app code: the commits after it change only the tests and the change log
Server programThe official WaterWall 1.5.42 release program, unchanged, the same program as our permanent test server, run as a test copy on port 4097
Server DNS lookups5 tries, WaterWall 1.5.42's default; the test copy's core.json does not set it
TrafficAn HTTPS test server on the same machine, port 28483
NetworkOur office broadband line, over the public internet

Gaps and limits

Evidence

Test caselifecycle-retry-reset-ww-00097-vless-tls
Run2026-11-10T10:58:13Z to 2026-11-10T11:08:39Z (UTC)
Step log times2026-11-10 14:03:57 to 2026-11-10 14:04:05 (phone time, UTC+3)
App sourcecommit e69cb668, Debug build
Server programWaterWall 1.5.42, the official release, unchanged, SHA-256 38631081bd10347d…
Evidence filewaterwall-lifecycle-20261110T1058Z.json