Fix testReconnectingTunnelRefreshesItsStatusios-allow-multiple-fulfillments

Since the simulated tunnel connection ends up always transitioning back
to the connected state, this test will fail due to fulfilling the
connected state expectation multiple times. The fix here is to not let
that happen in the first place by removing the listener as soon as we
see the expected state.

1 files changed, 4 insertions, 2 deletions

diff --git a/ios/MullvadVPNTests/MullvadVPN/TunnelManager/TunnelManagerTests.swift b/ios/MullvadVPNTests/MullvadVPN/TunnelManager/TunnelManagerTests.swift
index 557e40bbf2..30ca6a2576 100644
--- a/ios/MullvadVPNTests/MullvadVPN/TunnelManager/TunnelManagerTests.swift
+++ b/ios/MullvadVPNTests/MullvadVPN/TunnelManager/TunnelManagerTests.swift
@@ -222,10 +222,12 @@ class TunnelManagerTests: XCTestCase {
         let connectedExpectation = expectation(description: "Connected")
         let reconnectingExpectation = expectation(description: "Reconnecting")
         let tunnelObserver = TunnelBlockObserver(
-            didUpdateTunnelStatus: { _, tunnelStatus in
+            didUpdateTunnelStatus: { manager, tunnelStatus in
                 switch tunnelStatus.state {
                 case .connected: connectedExpectation.fulfill()
-                case .reconnecting: reconnectingExpectation.fulfill()
+                case .reconnecting:
+                    manager.removeObserver(self.tunnelObserver)
+                    reconnectingExpectation.fulfill()
                 default: return
                 }
             }