From b77323ce4baa3aca5afc0cf9e1fab5311f1fc124 Mon Sep 17 00:00:00 2001 From: vibesoftwarecoder Date: Mon, 5 Oct 2026 08:33:26 -0500 Subject: [PATCH] Fix CFBundleExecutable to match the renamed macOS target app.pro renamed the macOS build target from "Moonlight" to "MoonlightVibe" in 71009e96 (2026-05-01), but Info.plist's CFBundleExecutable was never updated and still names "Moonlight" - upstream's original value, untouched since e596c2dc. The real compiled binary has been "MoonlightVibe" in every fork release since. macdeployqt resolves the bundle's main executable via CFBundleExecutable, so it's been looking for Contents/MacOS/Moonlight, which has never existed - confirmed directly in CI logs: macdeployqt's first action on this bundle is "ERROR: Could not find bundle binary", immediately followed by a cascade of "Cannot resolve rpath" for essentially every Qt framework, because framework deployment never successfully ran against the (unfound) real binary. Upstream's own current CI has neither error. This is the most likely actual cause of #13 ("damaged or incomplete" on macOS) - a structurally incomplete bundle, independent of and pre-dating the ad-hoc-signing fix in #14/v6.3.7, which did not resolve the reporter's symptom because it signed an already-broken bundle. Co-Authored-By: Claude Sonnet 5 --- app/Info.plist | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/Info.plist b/app/Info.plist index 24980b7757..0665ee200a 100644 --- a/app/Info.plist +++ b/app/Info.plist @@ -5,7 +5,7 @@ GCSupportsGameMode CFBundleExecutable - Moonlight + MoonlightVibe LSSupportsGameMode CFBundleGetInfoString