From b1bcaea0dc714c5cfebbc7a6f9716c3c050cea16 Mon Sep 17 00:00:00 2001 From: Jason Schulz Date: Wed, 10 Jun 2026 17:07:26 -0400 Subject: [PATCH] fix: consistent weak capture of controller in first-launch closure The outer onReceive closure captured controller strongly while the nested onComplete closure declared [weak controller]; newer Swift toolchains (Xcode 26 beta) reject the mismatch under #ImplicitStrongCapture and the app target fails to build. Capture weakly at the outer closure as the nested one already intends. Co-Authored-By: Claude Fable 5 --- app/EXO/EXO/EXOApp.swift | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/EXO/EXO/EXOApp.swift b/app/EXO/EXO/EXOApp.swift index 5757b0ebae..f8a051ca88 100644 --- a/app/EXO/EXO/EXOApp.swift +++ b/app/EXO/EXO/EXOApp.swift @@ -71,7 +71,7 @@ struct EXOApp: App { .environmentObject(bugReportWindowController) } label: { menuBarIcon - .onReceive(controller.$isFirstLaunchReady) { ready in + .onReceive(controller.$isFirstLaunchReady) { [weak controller] ready in if ready { DispatchQueue.main.asyncAfter(deadline: .now() + 3.0) { self.firstLaunchPopout.onComplete = { [weak controller] in