Google Chrome Fleet-maintained app relaunches Chrome after a patch/update even when it had no open window (macOS)

[jakestenger]

Fleet versions

• Discovered: macOS, via the Google Chrome Fleet-maintained app. The relaunch logic lives in the FMA install script (synced from the maintained-apps manifest), so this is effectively independent of the Fleet server version — it affects any instance syncing the current Chrome FMA manifest. The relaunch was introduced in Add session restore to Google Chrome FMA updates #36662 (2025-12-04); the only change since is the shebang swap in Switch scripts to bash and update refs #44853.
• Reproduced: current Chrome FMA install script on main (logic unchanged as of this filing).

Web browser and operating system: Google Chrome on macOS

---

💥 Actual behavior

After Fleet patches/updates the Google Chrome Fleet-maintained app on macOS, Chrome launches (opening a window with the last session restored) even when the user had no Chrome window open at the time of the update.

🛠️ Expected behavior

Chrome should only be reopened after the update if it had an open window when the update started. If the user wasn't actively using Chrome, the update should complete without launching it.

🧑‍💻 Steps to reproduce

These steps:

• Have been confirmed to consistently lead to reproduction in multiple Fleet instances. (Check with @ddribeiro who confirmed the behavior)
• Describe the workflow that led to the error, but have not yet been reproduced in multiple Fleet instances.

1. Add the Google Chrome Fleet-maintained app to a team and enable it for update/patch (or self-service update).
2. On a macOS host, leave Chrome with a lingering background process but no visible window — e.g. "Continue running background apps when Google Chrome is closed" is enabled, or a background-mode extension is installed — then close all Chrome windows.
3. Trigger the Chrome update via Fleet.
4. Chrome launches with the previous session restored, even though no window was open beforehand.

🕯️ More info (optional)

Root cause appears to be in ee/maintained-apps/inputs/homebrew/scripts/google_chrome_install.sh: the script decides whether to relaunch based solely on osascript -e 'application id "com.google.Chrome" is running' (CHROME_WAS_RUNNING). That check returns true whenever Chrome has a background/helper process alive — even with no visible window — so the script reopens it.

This is the same symptom that was fixed for the VS Code FMA in #42732 / PR #42733, where the relaunch decision was changed to check for an actual visible window via System Events (window count > 0) instead of just "is running." The same approach would fix Chrome. (Chrome was explicitly left out of that change as "already handled correctly.")