ios: don't capture a mutable local in a @Sendable closure

MainActor.run's body is @Sendable, and the switched flag added in the previous commit was a var captured by it - which strict concurrency diagnoses. Assigning a let on both branches of the do/catch is definitely initialised and safe to capture anywhere, with no behaviour change.
2026-08-14 07:10:19 +00:00 · 2026-08-06 16:12:26 +00:00
parent 147955f52d
commit b9eb86541c
1 changed files with 5 additions and 1 deletions
@@ -281,12 +281,16 @@ struct ContextProfilePickerView: View {
            // resync to what the host actually did and report it. The failure is the
            // switch, not the creation, so it is not rethrown into the form's "error
            // creating profile" handler.
-            var switched = false
+            // let, not var: MainActor.run's body is @Sendable, and capturing a mutable
+            // local in one is diagnosed under strict concurrency. Assigned on both
+            // branches, so it is definitely initialised.
+            let switched: Bool
            do {
                try await changeActiveUserAsync_(newUser.userId, viewPwd: nil)
                switched = true
            } catch {
                logger.error("changeActiveUserAsync_ error: \(responseError(error))")
+                switched = false
            }
            await MainActor.run {
                // Only when the switch actually happened: the prepared chat then belongs