-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Repeated prompts to install helper on macOS Monterey #13956
Comments
Thanks for your report @obchodniuspech I don't exactly understand why it's asking for your password 🤔 We have released 3 new versions this week (2.9.7, 2.9.8 and 2.9.9) to address a few issues we've found, not sure if those many releases is why Desktop is bugging you. Could you upgrade to the latest version and see if it still requests your password? |
I just upgraded, it could leave me in peace for about 3 days and then when Iam working on project it asks for example 30 times in one afternoon :D its very scary and I event wanted to uninstall completely :D I will try the new version. I hope it will dissapear its very anoing :( |
Its happening again. Are there more helping tools for github or only one? What can I do for better debugging? |
There are no "tools", I'm not totally sure why it's prompting you the password so many times, other than to get access to your GitHub token (to keep you signed in). In the screenshot you shared the dialog says "there is an update ready to install", which shouldn't require admin permissions 🤔 Is the app correctly located in |
It says it want to install helper tool and update :D Yes, the app is in /Applications If its only my problem Im not sure what to do I will try to reinstall, when I will finish project Im working on cause Im too lazy to fill in the auths again :D |
just to let you know, on actual version it asks - like 4-6 times a day... kill me :D |
I have this same problem, and it was happening even before I upgraded to Monterey. In fact, it just happened when I was trying to sign in to leave this comment, and I had to enter my password 4 times in a row before it finally stopped! This is maddening! |
Also get this, most frequently with Github but also some other apps. |
Just want to chime in as I have the exact same issue. Github desktop is installed in /Applications but (for security reasons) I'm not normally logged in as admin and thus normally needs to enter admin user and password to write to the /Applications folder if that can make any difference. I also have two git accounts one for work and one private, if that can give any clues. I'm on an intel mac with MacOS 12.3.1 (Monteray) |
I get the prompt a minimum of three times after returning to my workstation after an extended period of time, i.e. a work day. These prompts don't actually say anything about the operation underway, and I reject them. A software update is not a helper application being installed, making it sufficiently suspicious. If I do bother with the dance in a VM, I'm asked a minimum of three times. Git on my machine is managed by Homebrew, I do not require (nor desire) graphical applications manipulating the contents of |
As mentioned before, GitHub Desktop shouldn't install any kind of tool… I'd only expect it to prompt for your macOS user password to read your GH token from the keychain. Also, GitHub Desktop bundles its own git but it's not available broadly, it's used only by GH Desktop. However, this is interesting:
Could you try installing it "normally" to |
Mine is installed in |
Mine too! |
Interesting note to add, even if it were attempting to install a utility helper under The prompt seems fairly clear to me that this isn't a Sparkle (automatic) update being applied. "Add a new helper tool" may be overly generic, though. Edit to add: and it's very insistent. Back to only having it running when actively in use—just like before the option to disable automatic fetch—I guess. Edit again: it really doesn't seem related to update installation. This morning I got the banner that an update was downloaded and ready to install, click to restart the app. After days of cancelling the |
I too have this problem.. it makes GitHub desktop unusable.. |
I have an office workstation and a home one. The provided description was from home, remains true at the office where I think the really fundamental question is: what the ████ is it doing requiring these prompts? I'm security-conscious (totally not an IT specialty), so unexpected prompts like these are serious warning flags. One of the security tools I use had a Sparkle update that failed to render all text on window widgets, I did not even attempt to permit it (outside an ephemeral sandbox VM) before confirming with the vendor that this was a known bug, and the update was legitimate. |
Thank you all for your feedback 🙇 @amcgregor again, AFAIK GitHub Desktop should prompt for anything unless you choose to install the CLI tool from Doing some search on Google, I see other people having the same prompt with other Electron apps like Slack, and changing the permissions of the In my case, it looks like this:
Could that be the issue you're facing? |
@sergiou87 Interesting; the @ in the permissions summary says there are XATTR ACLs present; the "UNIX permissions" don't tell the whole story in your case. It's also seemingly owned by you. At my office station, owned by the domain administrator's local representation:
Neither has XATTRs; at home:
This is, admittedly, quite strange. I'll blame the Migration Assistant on this one. ("Must quit all applications" is often code for "we're dropping down to a console session as root".) When I get home, I'll tweak these permissions and see if it makes a difference. Thanks for the pointer! (Pardon the edits; deep paths, man, and keeping the fenced blocks understandable. Self-modifying applications—requiring write permission to themselves—unrelated to software updates are another warning sign.) |
No worries, we're really grateful for all the detailed research you're doing!! As we were unable to reproduce this, we were completely clueless 😖 |
Found it. This appears (since I hit "record" after the prompt appeared…) when I cancel the prompt:
Backslashes added by me; originally a single line. I've now updated the permissions on-disk:
Group write enforced because I do actually want any user of the system able to update the application in a shared home folder overlay. Now to wait and see if the prompt re-appears or additional console output is detected relating to GitHub. My next step if this fails would have to be to attempt to apply custom XAttr ACLs (i.e. grant each user permission explicitly) or ultimately moving the application to a volume with "ignore owners" set as a failsafe. Does anyone have advice for multiuser environment deployments? [a few minutes later] And I notice no option to disable automatic updates, so no centralization of that task and elimination of the local periodic check. Edit to add: I did notice the file it was attempting to write to was deeply nested within the bundle, but failed to capture the exact path. |
And I can confirm permissions were my issue:
This notice appears important:
Asterisks mine. 😉 It continues:
This is all fairly cleaned up, and after this there's a good chunk of 🧈🥬💃 |
Yay! Thanks again for your detailed reports 🙇♂️ @obchodniuspech I hope this helps you too: you must make sure all files in Closing now… |
@obchodniuspech could you run You should see something like this:
|
Has the installer been updated to prevent this happening? Or instructions on how to install without this problem occurring? I found on 2 machines using the installer created this problem. |
@aussiemate32 I have no idea how this could happen to begin with 🤔 The first time a user installs this is by unpacking a zip and moving the Did you install it differently? I wonder what the difference actually was… 🤔 |
ls -l /Applications/ | grep Desktop |
@obchodniuspech thank you. As you see, How did you install GitHub Desktop exactly? I wonder if just deleting it entirely, and then downloading the latest version from https://desktop.github.com/ and installing it again would solve the issue. |
@obchodniuspech Have you restored your machine using Migration Assistant, by any chance? |
@amcgregor if you mean like when iam buying new mac, sure - i do this all the time. I dont have any other problems with other apps. |
I’m very new to GitHub. apologies I thought I’d installed it from an installer.. dmg type thingy.. I still have no idea how this happens.. |
Cool. That was the exact reason why my
It's very rare for an application to be self-modifying in this way. Most update systems notify of an update and request permission to install ("install now", "install on next start", &c.) thus give a clear indication of why a sudo (elevated permissions) prompt may appear. If the application being updated is not owned by your user account, clicking "update now" will immediately prompt for elevated permissions with a clear correlation and explanation for why you are being prompted. Most wouldn't think about it as being unusual in this type of case—often I don't even notice it for updates to things like my DBA tools or multimedia software. It's unusual in GitHub Desktop's case in that it attempts to silently write to its own internal files, triggering the prompt seemingly without reason. No "would you like to update now, or later" prompt which would give an indication as to the action underway which would require this. No way to disable automatic modification at all. (My domain administrator is not particularly happy about this fact.)
That was going to be one of my next steps. What you did was add your user account as an ACL (Access Control List) entry. I'm not entirely sure this permission gets inherited on files deeper within the bundle; try changing the owner instead: (this corrected the issue for me, though I did this from Terminal, not Finder) |
Hello, I have the same problem on Monterey 12.4. Is there a fix for that? |
I have the same problem on Montery 12.5.1, but it also existed many versions before that. $ groups lara
> staff admin ... $ groups work
> staff admin ... Before updating, I did: $ sudo chown -R root:admin GitHub\ Desktop.app
$ sudo chmod -R 775 GitHub\ Desktop.app Which results in: $ ls -l /Applications
> ...
> drwxrwxr-x 3 root admin 96 Aug 24 10:11 GitHub Desktop.app
> ... I then proceeded to update the app via the $ ls -l /Applications
> ...
> drwxr-xr-x 3 Work staff 96 Aug 24 10:11 GitHub Desktop.app
> ... This again leaves me with the problem that I will only be able to update the app without prompts from the Work account. As soon as I switch to my personal account the helper tool prompts will appear again. I also tried setting the user and group to I should note that the exact same behaviour can be observed with other Electron-based apps, like Visual Studio Code. I wonder if this can be fixed with ACL permissions, or if the solution is just to install every app twice. Any help would be appreciated.. :) |
While I appreciate that in single-user environments the problem appears to be less of a problem, the problem still exists, especially for managed workstations. The update mechanism is not transactional and attempts to authorise every individual on-disk file change operation. It can not be disabled and manually updated as a transaction. This isn't "fixed", it's "ignored". |
Same issue here after installing the 12.6 Monterey update. |
Ditto, I started running into this after upgrading to Monterey 12.6 |
same goes for me |
I also have this issue and if it helps at all, I also have it with VSCode, Zotero, and Evernote. Although GitHub seems to pop up most frequently (multiple times when opened and then occasionally through the day). I've also had this issue for a while now, including before installing Monterey (previously on Big Sur) |
This, we are still seeing this issue. Specifically on the latest version 3.2.3. End users can't change the user/owner permissions on |
Describe the bug
Every hour or two, Github desktop asks me for installing support tools....
Version & OS
Mac Os X Monterey
Github Desktop - Version 2.9.6 (arm64)
Open the 'About GitHub Desktop' menu to see the GitHub Desktop version. Also include what operating system you are using.
Steps to reproduce the behavior
Have open app in the background.
Expected behavior
Install the most once a week probably?
Actual behavior
Write a clear and concise description of what actually happened.
Screenshots
https://cln.sh/GS2vj7
Logs
2022-02-18T01:14:47.995Z - info: [ui] Executing getStatus: git --no-optional-locks status --untracked-files=all --branch --porcelain=2 -z (took 1.334s)
2022-02-18T10:09:39.385Z - info: [ui] Executing fetch: git -c credential.helper= -c protocol.version=2 fetch --progress --prune origin (took 3.814s)
2022-02-18T10:12:21.435Z - info: [ui] [BranchPruner] Last prune took place in 13 hours - skipping
2022-02-18T11:51:47.171Z - info: [ui] Executing fetch: git -c credential.helper= -c protocol.version=2 fetch --progress --prune origin (took 3.795s)
2022-02-18T14:12:24.413Z - info: [ui] [BranchPruner] Last prune took place in 9 hours - skipping
2022-02-18T15:18:43.319Z - info: [ui] Executing fetch: git -c credential.helper= -c protocol.version=2 fetch --progress --prune origin (took 3.060s)
2022-02-18T18:10:17.997Z - info: [ui] Executing fetch: git -c credential.helper= -c protocol.version=2 fetch --progress --prune origin (took 1.219s)
2022-02-18T18:12:29.026Z - info: [ui] [BranchPruner] Last prune took place in 4 hours - skipping
2022-02-18T19:52:57.005Z - info: [ui] Executing fetch: git -c credential.helper= -c protocol.version=2 fetch --progress --prune origin (took 1.046s)
2022-02-18T21:02:01.106Z - info: [ui] Executing fetch: git -c credential.helper= -c protocol.version=2 fetch --progress --prune origin (took 4.035s)
2022-02-18T22:12:22.753Z - info: [ui] [BranchPruner] Last prune took place in 30 minutes - skipping
2022-02-20T12:14:05.764Z - info: [ui] [BranchPruner] No branches to prune.
2022-02-20T12:14:08.282Z - info: [ui] Executing getStatus: git --no-optional-locks status --untracked-files=all --branch --porcelain=2 -z (took 1.199s)
2022-02-20T12:22:02.923Z - info: [ui] Executing getStatus: git --no-optional-locks status --untracked-files=all --branch --porcelain=2 -z (took 1.118s)
2022-02-20T12:22:08.231Z - info: [ui] Executing getStatus: git --no-optional-locks status --untracked-files=all --branch --porcelain=2 -z (took 4.646s)
2022-02-20T12:22:08.794Z - info: [ui] [RepositoryIndicatorUpdater]: Refreshing sidebar indicators for 13 repositories took 12.9s of which 470.3s paused, total 483.2s
The text was updated successfully, but these errors were encountered: