Open matkoch opened 10 months ago
Can you please include the details from brew config
as it helps to diagnose the issue knowing which software / hardware your system utilises.
HOMEBREW_VERSION: 4.1.23
ORIGIN: https://github.com/Homebrew/brew
HEAD: fc259153591a309e2b6fee6f971eb61b16a3b6c0
Last commit: 12 hours ago
Core tap JSON: 05 Dec 07:01 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 10
Homebrew Ruby: 3.1.4 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.1.4/bin/ruby
CPU: 10-core 64-bit arm_firestorm_icestorm
Clang: 15.0.0 build 1500
Git: 2.40.0 => /opt/homebrew/bin/git
Curl: 8.1.2 => /usr/bin/curl
macOS: 14.0-arm64
CLT: N/A
Xcode: 15.0.1
Rosetta 2: false
@matkoch I can replicate this issue, I'm not sure of the issue but it seems to be do with Quarantine. I'll look into it further tomorrow.
Is this issue with the most up to date version of Spotify? Looks like the software was updated on 24-Nov, which is after the date of download in the original screenshot. If not, can you update and see if this is replicated?
I also assume this is the Apple Silicon native version of Spotify, and not the Intel version with Rosetta?
I wasn't able to replicate this, unfortunately. (I know, not helpful.) I don't use Spotify anymore; I installed on a machine that has never had it. But no issues with brew install
and launching.
Interestingly I have seen this issue before, but got around it with a quarantine method that I will not recommend. But it seems that after uninstalling, and doing a full clean install the issue does not persist.
Yeah, I wasn't going to post as I didn't think it would be helpful, but thought a data point from never having it installed and being successful might point to something wrong for an upgrade workflow.
@krehel the screenshots are from yesterday. I also did a brew uninstall
and brew install
right before. Idk why the screenshots still mention Nov 20.
I encounter this today as well with the very latest version on my Intel MBP.
But it is not the first time I have this with Spotify. I have had this with some of the previous version too. In such case, I open System Settings
and go to Privacy & Security
. After the previous dialog, you should see the following:
After clicking Open Anyway
, you get the macOS cannot verify...
dialog again. If you click on Open
there, Spotify launches.
All in all, Spotify should be verified company. The steps above don't feel safe & shouldn't be needed
FYI, the "Open Anyway" did NOT fix it for me. I should've included that in the OP.
Had the same issue here on an M1 Mac. uninstall
and then install
again fixed it for me (reinstall
didn't).
Had the same issue here on an M1 Mac.
uninstall
and theninstall
again fixed it for me (reinstall
didn't).
Same problem here, but on an Intel Mac. uninstall
and install
fixed it for me as well:
tdeutsch at thor in ~
$ brew uninstall spotify
==> Uninstalling Cask spotify
==> Removing launchctl service com.spotify.webhelper
Password:
==> Backing App 'Spotify.app' up to '/usr/local/Caskroom/spotify/1.2.26.1187,36b
==> Removing App '/Applications/Spotify.app'
==> Purging files for version 1.2.26.1187,36b715a1,270 of Cask spotify
tdeutsch at thor in ~
$ brew install spotify
Running `brew update --auto-update`...
Installing from the API is now the default behaviour!
You can save space and time by running:
brew untap homebrew/core
brew untap homebrew/cask
==> Auto-updated Homebrew!
Updated 4 taps (aquasecurity/trivy, homebrew/cask-versions, homebrew/cask-fonts and homebrew/cask).
==> New Casks
font-playwrite-co font-playwrite-fr-trad sakura
You have 4 outdated formulae installed.
==> Downloading https://download.scdn.co/Spotify.dmg
###################################################################################################################################################################### 100.0%
Warning: No checksum defined for cask 'spotify', skipping verification.
==> Installing Cask spotify
==> Moving App 'Spotify.app' to '/Applications/Spotify.app'
🍺 spotify was successfully installed!
MacOS only asked if I really want to open this app downloaded by cask from the internet. This was a one time only dialog, next start of Spotify was without any dialogs.
Today, this cannot be verified
error started to happen for cask warp
on my M1 MacBook Pro also. An uninstall
, cleanup
and install
(not reinstall
) worked to resolve it, but it is quite annoying having to do this.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
This is definitely not stale. I'm having this issue once in every two weeks.
Apologies for the issue going stale, and we appreciate everyone's patience. We are looking into this and believe we have a lead on why it's happening. More to come.
Looking forward to the direction you are investigating, @p-linnane. Bumped into this problem again today and would really see this fixed. It is so annoying.
Did you do anything specific before it happened again? Trying to establish how to replicate the issue consistently
From time to time, I upgrade all my casks using brew-cask-upgrade. When I run brew cu --all
, I see which ones need an update. A few days ago, I picked up this new release of Spotify.
Current output from brew cu --all
for Spotify:
26/33 spotify 1.2.30.1135 1.2.30.1135 Y [ OK ]
Since then, my Spotify setup is broken again with the cannot be verified
error again. A brew reinstall --cask spotify
doesn't help.
Thanks for the info. You can fix it temporarily by running brew uninstall spotify and then brew install spotify
Thanks for the info. You can fix it temporarily by running brew uninstall spotify and then brew install spotify
This doesn't surpass the problem for me. I also had to clean the cache and restart the device to get rid of that error.
This is a super annoying issue.
I uninstalled the app and ran brew cleanup
but that still doesn't get rid of the message loop.
How can you get this message for an app that doesn't even exist on the system!?
Same issue with spotify happened to me today. brew uninstall --cask spotify
, brew cleanup
, and brew install --cask spotify
helped, but it's annoying. This definitely should be fixed.
It looks like the issue started happening after upgrading MacOS from 14.4 to 14.4.1. Maybe some system files that were modified by Brew get overridden during the update?
Thanks for your patience, everyone! We're pushing a change that hopefully fixes the issue. If people are still having an issue, please let me know. Please also provide the output of:
launchctl list | grep spotify
as well as any Spotify-related Console logs.
@razvanazamfirei, unfortunately, today got a new update, and the same issue happened.
➜ ~ launchctl list | grep spotify ✔
26255 0 application.com.spotify.client.138935288.141593500
I also had the issue with the latest update, but the error message appeared less often. I think it was only once, I wasn't exactly watching for it but it was definitely not frustrating as before.
Tried a bunch of uninstall/cleanup/update/reinstall but nothing changed.
What did it for me was to disable Spotify in the Login Items
-> Allow in the Background
list, the app still works so all good I guess?
@razvanazamfirei, I've got a new update today, and this time, Spotify was running while I ran brew upgrade --cask.
==> Upgrading 1 outdated package:
spotify 1.2.34.783,923721d9,4676 -> 1.2.35.663,b699649e,5769
After the upgrade, I re-launched my Spotify, and everything worked fine—it just launched. Now, I'm confused. This behavior may be broken when the Spotify app is not running during upgrade.
Edit: Today, I got another update, and Spotify wasn't running at that time. After the upgrade, I tried to open Spotify, and got this issue again:
So it looks like the issue appear only when Stotify app is closed
```
default 13:56:21.123498+0300 runningboardd Launch request for app
After pressing "cancel" button, I got the following logs:
```
default 13:58:29.739398+0300 tccd AUTHREQ_ATTRIBUTION: msgID=515.160, attribution={accessing={TCCDProcess: identifier=com.spotify.client, pid=46169, auid=501, euid=501, binary_path=/Applications/Spotify.app/Contents/MacOS/Spotify}, requesting={TCCDProcess: identifier=com.apple.syspolicyd, pid=515, auid=0, euid=0, binary_path=/usr/libexec/syspolicyd}, },
default 13:58:29.750466+0300 tccd AUTHREQ_SUBJECT: msgID=515.160, subject=com.spotify.client,
default 13:58:29.751527+0300 tccd -[TCCDAccessIdentity staticCode]: static code for: identifier com.spotify.client, type: 0: 0x12cb48700 at /Applications/Spotify.app
default 13:58:29.756105+0300 kernel ASP: Security policy would not allow process: 46169, /Applications/Spotify.app/Contents/MacOS/Spotify
default 13:58:29.758927+0300 runningboardd [app
For me a new entry below Settings -> Gatekeeper -> Allow applications downloaded from "App Store and identified developers
appears after starting spotify with the same prompt as seen in the issue description. Where I could approve spotify. After that when starting a new option appeared to open spotify anyway.
I got confused... Today got another update (spotify 1.2.36.959,04bf500c,859 -> 1.2.37.701,e66eb7bc,1226), and Spotify was stopped at that moment. After the upgrade, I tried to open Spotify and... it just works... Looks like it's not related to the fact that the app is running or no.
I have the same issue, for me emptying the trash and running brew reinstall spotify
does the trick. From what I gather there's a Spotify agent running in the background that's still the old version in the trash
I don't have a screenshot of that anymore (it's been a couple months) but I tracked down the error log in Console and that pointed to an executable in a trashed version of Spotify.app
Still experiencing this issue, any updates on the cause please?
Brew config:
HOMEBREW_VERSION: 4.3.7
ORIGIN: https://github.com/Homebrew/brew
HEAD: 43eaeca50fe3b6c755f3fc9bc6f43669e0db1039
Last commit: 5 hours ago
Core tap JSON: 24 Jun 13:03 UTC
Core cask tap JSON: 24 Jun 13:03 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 10
Homebrew Ruby: 3.3.3 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.3/bin/ruby
CPU: 10-core 64-bit arm_firestorm_icestorm
Clang: 15.0.0 build 1500
Git: 2.45.2 => /opt/homebrew/bin/git
Curl: 8.6.0 => /usr/bin/curl
macOS: 14.5-arm64
CLT: 15.3.0.0.1.1708646388
Xcode: 15.3 => /Applications/Xcode-15.3.0.app/Contents/Developer
Rosetta 2: false
Just like @matkoch mentioned in the description:
[...] after disabling Spotify from login items, it stops happening.
So just:
1) Open System Settings > Login Items, and toggle off Spotify.
2) Click on "Cancel" in the "cannot be verified" dialog.
The root cause is that Homebrew was leaving the old Spotify login item when removing or upgrading the app.
This seem to be fixed by PR #170742, which is already merged.
After this fix, when removing Spotify, you should see the startup service being successfully removed:
$ brew uninstall --cask spotify
[...]
==> Removing launchctl service com.spotify.client.startuphelper
[...]
Now you can just reinstall Spotify.
I just hit this again, despite previously running brew uninstall spotify and seeing the startuphelper being removed. Are we sure this is fixed?
For me a new entry below
Settings -> Gatekeeper -> Allow applications downloaded from "App Store and identified developers
appears after starting spotify with the same prompt as seen in the issue description. Where I could approve spotify. After that when starting a new option appeared to open spotify anyway.
This still works every time for me
Open Anyway
Open
in the unidentified application dialogFor whatever reason, the Spotify binary that hombrew is getting is not signed as from a legitimate developer. This is confusing to me, because it seems as though people downloading it directly from their browser (and installing it the old fashioned way) aren't also having this issue. Unless they are? I doubt it.
Happened again today, this fixed it, but this should not be the permanent solution:
brew uninstall --cask spotify && brew cleanup && brew install --cask spotify
Just happen to me again.
Only brew uninstall --cask spotify && brew cleanup && brew install --cask spotify
helps to run it again.
Workaround
Just like @matkoch mentioned in the description:
[...] after disabling Spotify from login items, it stops happening.
So just:
1. Open System Settings > Login Items, and toggle off Spotify. 2. Click on "Cancel" in the "cannot be verified" dialog.
Definitive fix
The root cause is that Homebrew was leaving the old Spotify login item when removing or upgrading the app.
This seem to be fixed by PR #170742, which is already merged.
After this fix, when removing Spotify, you should see the startup service being successfully removed:
$ brew uninstall --cask spotify [...] ==> Removing launchctl service com.spotify.client.startuphelper [...]
Now you can just reinstall Spotify.
Mentioned definitive fix is not definite.
Just happen to me again. Only
brew uninstall --cask spotify && brew cleanup && brew install --cask spotify
helps to run it again. Mentioned definitive fix is not definite.
Same, I'm still getting it and this is the only workaround.
I also tried brew uninstall --cask spotify && brew cleanup && brew install --cask spotify
to no avail. When I do
brew uninstall --cask spotify && brew cleanup
launchctl list | grep spotify
1878 -9 com.spotify.client.startuphelper
so the helper is still there!
My solution was to do BOTH workarounds:
brew uninstall --cask spotify && brew cleanup
brew install --cask spotify
That may be belt and braces but it did seem to work
3 weeks later.
I literally created an alias alias spor="brew uninstall --cask spotify && brew cleanup && brew install --cask spotify"
@bevanjkay
So on 5th of September Spotify was running and playing.
I run brew upgrade --greedy && brew cleanup
and Spotify has updated. Since that day i had no Mac restarts, only sleep mode, until yesterday i shut it down.
Spotify is in autostart, today i launched my Mac, result is on screenshot.
More over, this window prevents me from manual start of any other application.
Canceling is in constant loop, until i click Move to bin.
Thanks for the info @noizo It seems that a computer restart might be key in replicating the issue - but this isn't consistent for me. The biggest hurdle for me has been not being able to replicate it regularly which has made this difficult to chase down.
I'm trying another launchctl
removal, but I'm not convinced it will fix the issue - we will know after the next rounds of updates.
Not sure if you've tried this, but it happens when I do a brew upgrade
. so you could uninstall, install the previous version, then brew upgrade spotify
.
@arro Definitely seems like the best way to go, I just haven't had access to a previous version of the Spotify application. I have a backup of the current one now, so can do some testing when there's another version bump.
Just want to update - I got the same issue today, after upgrading to macOS Sequoia. Before that, I hadn'y any issues for a few months. Not sure if that's a new issue, but looks the same as previously.
@Arro I don't think that downgrade is possible, the download link is always the same - https://download.scdn.co/SpotifyARM64.dmg
I got the same issue today, after upgrading to macOS Sequoia. Before that, I hadn't any issues for a few months.
It's exactly the same case here. Uninstall, clean purge and install solved it this time, but it was still annoying.
I had no issues with Spotify after upgrading to Sequoia.
But last time i executed:
launchctl remove com.spotify.client.startuphelper
after removal.
brew uninstall --cask spotify
brew cleanup
launchctl remove com.spotify.client.startuphelper
brew install --cask spotify
seems like it works for now.
Interesting finding @noizo - this would suggest that the launchctl item is not being successfully removed from the cask.
launchctl remove com.spotify.client.startuphelper
- this command is ran during uninstall.
Verification
--force
.brew update-reset && brew update
and retried my command.brew doctor
, fixed as many issues as possible and retried my command.Description of issue
I've updated Spotify about 2 weeks ago. I'm not sure I restarted my system since then, but once I did today, I'm in an endless loop of this dialog:
It doesn't matter what option I choose, after 10 seconds, the dialog appears again (and steals focus).
I tried
brew uninstall
(with force), but it kept happening.I noticed that after disabling Spotify from login items, it stops happening.
Command that failed
brew uninstall --cask spotify --force
Output of command with
--verbose --debug
Output of
brew doctor
andbrew config
Output of
brew tap