Announcements

SOLVED [macOS] Cannot pause or play Spotify using space bar after minimizing using Command+W

Solved!

SOLVED [macOS] Cannot pause or play Spotify using space bar after minimizing using Command+W

Issue Solved as of latest Spotify Desktop version

If not prompted for update, navigate to top-left corner -> Spotify -> About Spotify -> "There is a new update available"

 

Device

M1 MacBook Air 2020

Operating System

macOS Big Sur 11.5.2

My Question or Issue

After hiding / minimizing Spotify using Command+W (on macOS), play/pause functionality with the space bar does not work until clicking on the Spotify UI to fully focus the application. Other Spotify hotkeys such as Command+Left Arrow and Command+Right Arrow still function in this state, but not the space bar for play/pause. A demonstration of the issue can be found below.

 

Video of the Issue (w/ Audio)

https://www.youtube.com/watch?v=oLHL7jwh_7g&ab_channel=AlfoKenny 

 

I should note that this was not an issue before. This is a relatively new issue that got so unbearable I had to submit a bug report about it.

Reply

Accepted Solutions
Marked as solution

This issue has been solved as of the latest version of Spotify.

 

If not prompted for updatenavigate to top-left corner in Apple top bar -> Spotify -> About Spotify -> "There is a new update available".

 

Thanks to everyone for making this issue known to the developers who ultimately implemented a fix 😀

View solution in original post

20 Replies

I'm glad it's not just me. Spacebar also doesn't work if you've just CMD+Tab'd away from the app and back again. I've seen the problem on two different Macs, one running Mojave and the other running Catalina.

Glad I'm not the only one then! Hopefully this gets fixed soon

Hey folks,


Thanks for reaching out about this in the Community and for the video recording.

 

Can you please let us know the following, if you haven't done already:

  • Device model, OS version 
  • Spotify version

Looking forward to your replies.

AlexModerator
Help others find this answer and click "Accept as Solution".
If you appreciate an answer, maybe give it a Like.
Are you new to the Community? Take a moment to introduce yourself!

This is also happening for me.

M1 MBA: MacOS 12.3.1 (21E258)

Spotify for macOS (Apple Silicon): 1.1.84.716.gc5f8b819

Intel MacBook Pro 15in: MacOS 10.14.6
Spotify for MacOS (Intel): 1.1.84.716.gc5f8b819

Model: MacBook Air (M1, 2020), macOS Big Sur 11.5.2

Spotify Version: [

Spotify for macOS (Apple Silicon)
1.1.84.716.gc5f8b81

]

Also happening on my 2018 Intel Mac Mini (paired to an external Radeon RX 580) @ 64GB RAM. Catalina 10.15.7 with Spotify version 1.1.84.716.gc5f8b819

Also happening to me: 2018 Intel Mac Mini - Monterey 12.3.1. Spotify version: 'Spotify for macOS (Intel)
1.1.84.716.gc5f8b819'.

MacBook Pro (14-inch, 2021)
12.3.1 (21E258)

Same here.  M1 Ultra 12.3.1

Same issue here (although it seems to be whenever another app has been focused, then I click on the Spotify dock icon, i.e. not only after Cmd+W).

MacBook Pro (16-inch, 2019)

Big Sur 11.6.5

Spotify version 1.1.84.716.gc5f8b819

Any update on this issue?

I've been experiencing this on multiple Macs. Currently on

MacBook Pro (16-inch, 2021)

MacOS 12.3.1 (21E258)

Spotify for macOS (Apple Silicon) 1.1.84.716.gc5f8b819

Happening for me too.

 

MBP Retina 15-inch Mid 2015, macOS Monterey 12.3.1

Spotify for macOS (Intel)
1.1.84.716.gc5f8b819

I believe the newest update fixed this!

Spotify for macOS (Intel)
1.1.85.895.g2a71e1b8

Just did a clean re-install.  Did not fix.  Still on a M1 Ultra 12.3.1.  

Spotify for macOS (Apple Silicon)
1.1.84.716.gc5f8b819

As Galaxia pointed out above, it seems to be fixed!
Spotify for macOS (Intel)
1.1.85.895.g2a71e1b8

Yep, fixed with v1.1.85.895.g2a71e1b8!
Marked as solution

This issue has been solved as of the latest version of Spotify.

 

If not prompted for updatenavigate to top-left corner in Apple top bar -> Spotify -> About Spotify -> "There is a new update available".

 

Thanks to everyone for making this issue known to the developers who ultimately implemented a fix 😀

Suggested posts