SRTP-WRAP-A Device ID (build 181)
- The device identifier that SRTP-WRAP-A sends to the server is now a normal
per-server field: visible and editable in the server editor, and stored in
Full Backup. It used to be a single hidden value shared by every
configuration and absent from backups. - The server ties the WireGuard peer and tunnel IP it hands you to this value,
so leave it alone unless you want a separate registration on the server —
changing it gets you a new address inside the tunnel. - Your existing device ID is carried over automatically, so a WRAP-A server
keeps the peer it already had. Connection links still do not contain it (it
identifies your device, not the deployment), so importing a link mints a
fresh one.
VK account (cookie) mode: the connection cap now really applies (build 182)
- In VK-account mode the app has always shown a cap of about 20 connections
per call link, but the tunnel still started with the full number you had
configured. The surplus connections could never get credentials and retried
in a loop for the whole session. - The cap is now applied where the count is handed to the tunnel. Your stored
Connections setting is untouched — add another call link and the full number
is used again.
wdtt:// links (build 183)
- Importing a wdtt:// link now builds the VK call link on vk.ru instead of
vk.com, matching the rest of the app after VK's domain migration.
Re-signed builds now explain themselves (builds 184-186)
If you installed this app from an IPA that was re-signed by a third-party
signing service, the app could not previously tell you that anything was wrong:
the log screen was empty, every statistic read 0, and the SRTP-WRAP-A device ID
was not kept between launches — while the VPN itself worked normally.
The cause is that a re-signer replaces the app's signing identity with its own,
and the shared storage area the app and the tunnel extension use to talk to each
other belongs to the team that registered it — it cannot be carried over. The
same substitution also blocks the direct channel between the app and the
extension, which is where the statistics come from.
- The Logs screen now names the team that signed your build and the storage
areas it actually has, instead of a generic "entitlement missing" message. - Statistics coming from the tunnel show "—" with a short explanation instead
of zeros that looked like a dead VPN. - The log export no longer labels the app's own lines as if the tunnel
extension had written them, and says when the extension's lines could not be
collected at all.
This release does not make a re-signed build work — that is not possible from
inside the app. Install through TestFlight for a build with everything enabled.