-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Software update popup should not be presented during Sparkle update process #9562
Comments
Reproduced the issue on STR:
|
I can't reproduce this issue with an admin user. But it reproduces immediately when Brave is installed in |
I believe the problem is that Sparkle (at least in our version 1.x) checks for writeability of the app directory before performing a background update. Our call stack: This last call checks the writeability. If the app directory is not writeable, then |
Also in Sparkle 2, the analogous
This makes me believe that it is unlikely that upgrading to Sparkle 2 would fix the problem. |
@mihaiplesa @bsclifton I think we may be hitting a "by design" issue here. Can I get input from you (and potentially other people you might tag)? As this issue explains, Brave on macOS shows an unnecessary "Update Available" popup when run as non-admin user and an update becomes available: But consider the constraints: A non-admin user tries to update a usually system-wide installation of Brave. This is not possible without admin rights. What happens when the non-admin user selects that the update should be installed is that after a restart of Brave they get the following dialog: If they don't have any admin credentials (or cancel the dialog for another reason), then the dialog disappears and Brave does not launch. Brave can be started again, but runs at the old version. I can think of the following options for addressing this issue. They are quite different in their UX and implications:
What do you think we should do? |
@diracdeltas Thoughts on the options @mherrmann proposed here: #9562 (comment) |
option 3 also sounds like the best compromise to me |
@mherrmann @mihaiplesa Let's proceed with option 3 here. |
@brave/legacy_qa when testing this on macOS we should be sure to do multiple checks (x64 v arm64 as well as different versions:
|
Verification for Using .pkg - FAILED
Logged #21813 for this Using .dmg - PASSED
Remove as many Brave artifacts from previous installations as possible (.app from Applications, profile folder from Application Support, Cache folder from Caches, com.brave.Browser.* from Caches, com.brave.Browser.* from Caches/Preferences)
Using .pkg - FAILED
Remove as many Brave artifacts from previous installations as possible (.app from Applications, profile folder from Application Support/BraveSoftware, corresponding ache folder from Caches/BraveSoftware, com.brave.Browser.* folder from Caches, com.brave.Browser.* from Caches/Preferences)
Note, this also happens on 1.36.x but with additional update prompts, so this is a better experience for the user than it was previously. Updated #21813 with this case. Using .dmg - PASSED
Remove as many Brave artifacts from previous installations as possible (.app from Applications, profile folder from Application Support/BraveSoftware, corresponding ache folder from Caches/BraveSoftware, com.brave.Browser.* folder from Caches, com.brave.Browser.* from Caches/Preferences)
Using .pkg - FAILED
Remove as many Brave artifacts from previous installations as possible (.app from Applications, profile folder from Application Support/BraveSoftware, corresponding ache folder from Caches/BraveSoftware, com.brave.Browser.* folder from Caches, com.brave.Browser.* from Caches/Preferences)
Added this case to #21813 Using .dmg - PASSED
Remove as many Brave artifacts from previous installations as possible (.app from Applications, profile folder from Application Support/BraveSoftware, corresponding ache folder from Caches/BraveSoftware, com.brave.Browser.* folder from Caches, com.brave.Browser.* from Caches/Preferences)
Using .pkg - PASSED
Remove as many Brave artifacts from previous installations as possible (.app from Applications, profile folder from Application Support/BraveSoftware, corresponding ache folder from Caches/BraveSoftware, com.brave.Browser.* folder from Caches, com.brave.Browser.* from Caches/Preferences)
Using .dmg - PASSED
Remove as many Brave artifacts from previous installations as possible (.app from Applications, profile folder from Application Support/BraveSoftware, corresponding ache folder from Caches/BraveSoftware, com.brave.Browser.* folder from Caches, com.brave.Browser.* from Caches/Preferences)
Using .pkg - FAILED
Remove as many Brave artifacts from previous installations as possible (.app from Applications, profile folder from Application Support/BraveSoftware, corresponding ache folder from Caches/BraveSoftware, com.brave.Browser.* folder from Caches, com.brave.Browser.* from Caches/Preferences)
Per brave/brave-core#12335 there shouldn't be any popup and there shouldn't be an update applied/offered. Added this case to #21813. Using .dmg - FAILED
Remove as many Brave artifacts from previous installations as possible (.app from Applications, profile folder from Application Support/BraveSoftware, corresponding ache folder from Caches/BraveSoftware, com.brave.Browser.* folder from Caches, com.brave.Browser.* from Caches/Preferences)
Per brave/brave-core#12335 there shouldn't be any popup and there shouldn't be an update applied/offered. Added this case to #21813. Follow up issue(s): Logged #21813 |
M1, Big SurVerification Using .dmg - PASSED
Actual Result: Got the
Using .dmg - PASSED
Actual Result: Was prompted to log in as Admin to elevate permissions, to install.
Using .dmg - PASSED
Actual Results: Got
Using .dmg - PASSED
Actual Results: Got
Actual Results: Got |
Verification for Using .pkg - FAILED
Using .dmg - PASSED
Remove as many Brave artifacts from previous installations as possible (.app from Applications, profile folder from Application Support, Cache folder from Caches, com.brave.Browser.* from Caches, com.brave.Browser.* from Caches/Preferences)
Using .pkg - FAILED
Remove as many Brave artifacts from previous installations as possible (.app from Applications, profile folder from Application Support/BraveSoftware, corresponding ache folder from Caches/BraveSoftware, com.brave.Browser.* folder from Caches, com.brave.Browser.* from Caches/Preferences)
Using .dmg - PASSED
Remove as many Brave artifacts from previous installations as possible (.app from Applications, profile folder from Application Support/BraveSoftware, corresponding ache folder from Caches/BraveSoftware, com.brave.Browser.* folder from Caches, com.brave.Browser.* from Caches/Preferences)
Using .pkg - FAILED
Remove as many Brave artifacts from previous installations as possible (.app from Applications, profile folder from Application Support/BraveSoftware, corresponding ache folder from Caches/BraveSoftware, com.brave.Browser.* folder from Caches, com.brave.Browser.* from Caches/Preferences)
Added this case to #21813 Using .dmg - FAILED
Remove as many Brave artifacts from previous installations as possible (.app from Applications, profile folder from Application Support/BraveSoftware, corresponding ache folder from Caches/BraveSoftware, com.brave.Browser.* folder from Caches, com.brave.Browser.* from Caches/Preferences)
Using .pkg - FAILED
Remove as many Brave artifacts from previous installations as possible (.app from Applications, profile folder from Application Support/BraveSoftware, corresponding ache folder from Caches/BraveSoftware, com.brave.Browser.* folder from Caches, com.brave.Browser.* from Caches/Preferences)
Using .dmg - PASSED
Remove as many Brave artifacts from previous installations as possible (.app from Applications, profile folder from Application Support/BraveSoftware, corresponding ache folder from Caches/BraveSoftware, com.brave.Browser.* folder from Caches, com.brave.Browser.* from Caches/Preferences)
Using .pkg - FAILED
Remove as many Brave artifacts from previous installations as possible (.app from Applications, profile folder from Application Support/BraveSoftware, corresponding ache folder from Caches/BraveSoftware, com.brave.Browser.* folder from Caches, com.brave.Browser.* from Caches/Preferences)
Per brave/brave-core#12335 there shouldn't be any popup and there shouldn't be an update applied/offered.
Using .dmg - FAILED
Remove as many Brave artifacts from previous installations as possible (.app from Applications, profile folder from Application Support/BraveSoftware, corresponding ache folder from Caches/BraveSoftware, com.brave.Browser.* folder from Caches, com.brave.Browser.* from Caches/Preferences)
Per brave/brave-core#12335 there shouldn't be any popup and there shouldn't be an update applied/offered.
Follow up issue(s): Logged #21813 to cover failed cases |
Intel, Big SurVerification Using .dmg - PASSED
Actual Results:Got
Using .dmg - PASSED
Using .dmg - PASSED
Actual Results:Unable to launch Brave after updating, stack from console is:
Using .dmg - PASSED
Actual Results:Confirmed I was NOT updated automatically example
Actual Results:Confirmed I was NOT updated automatically
|
Verification PASSED on Using .dmg - PASSED
Using .pkg - FAILED
Using .dmg - PASSED
Remove as many Brave artifacts from previous installations as possible (.app from Applications, profile folder from Application Support/BraveSoftware, corresponding ache folder from Caches/BraveSoftware, com.brave.Browser.* folder from Caches, com.brave.Browser.* from Caches/Preferences)
Using .pkg - FAILED
Remove as many Brave artifacts from previous installations as possible (.app from Applications, profile folder from Application Support/BraveSoftware, corresponding ache folder from Caches/BraveSoftware, com.brave.Browser.* folder from Caches, com.brave.Browser.* from Caches/Preferences)
Received the "Update available prompt/window" Using .pkg - FAILED
Remove as many Brave artifacts from previous installations as possible (.app from Applications, profile folder from Application Support/BraveSoftware, corresponding ache folder from Caches/BraveSoftware, com.brave.Browser.* folder from Caches, com.brave.Browser.* from Caches/Preferences)
Using .dmg - FAILED
Remove as many Brave artifacts from previous installations as possible (.app from Applications, profile folder from Application Support/BraveSoftware, corresponding ache folder from Caches/BraveSoftware, com.brave.Browser.* folder from Caches, com.brave.Browser.* from Caches/Preferences)
|
Verified
on QA:
|
User reported this still happens - https://twitter.com/patrick99e99/status/1581458270295756800 |
User further reported that they are admin and used the The initial fix for this issue consisted of two PRs:
The latter in particularly disabled popups for We should try to reproduce the scenario - unwanted popups when |
@mihaiplesa and I were unable to reproduce the issue on his macOS machine with a clean admin install via |
My current suspicion is that the user is still seeing the popups because of an old, persisted Sparkle preference. I've asked them on Twitter to clear the Sparkle preferences. They said they will report back to us. |
This issue is closely related to #39567. |
In issue #9274 there is discussion of the Changelog content which is raw html. That issue notes that Brave should simply update in the background and not present a choice to the user to install the update, skip it or remind them later.
This might be a permissions issue with Sparkle (described here). We will investigate this and attempt to make it auto update for all cases.
The text was updated successfully, but these errors were encountered: