WatchOS 10 makes playing music on watch so much more tedious

I (presumably like many others) have always used my watch to listen to music and track my runs.


WatchOS has progressively gotten worse in being easy and obvious to play music from the watch, if you try to start it while it is in range of your phone. It defaults to try and start music by controlling the phone. I got used to it but it was always annoying.


Now with WatchOS10 it makes it REALLY unintuitive and cumbersome.


Here are the steps I have to do to start my music. The music.app is a complication on my main watch face specifically so I can easily start music before a run. (This assumes that I am in range of my phone when I want to start the music which I always am at the beginning of my run and have played music on my phone since the last time I played it on my watch, which will always be the case)


  1. Hit music
  2. Hit the 3 little dots in the upper right
  3. Hit airplay
  4. Scroll all the way to the bottom of the device list (of which I have many because this is showing every airplay destination my phone currently sees)
  5. Hit "Control other speakers & TVs"
  6. Hit Apple watch
  7. Hit play


That's really unintuitive and a crazy amount of steps and to do every time I want to go for a run.


Am I missing something?

They seemed to have completely overlooking people using their watch this way despite all the previous ads for working out/running while listening to music.


Posted on Sep 29, 2023 3:52 PM

Reply
Question marked as Top-ranking reply

Posted on Dec 30, 2023 9:21 AM

Newsdude, on the watch, go to setting, general, handoff and turn « enable handoff «  off. It did it for me, but like you, I still have the problem with the app not remembering the last song played, and the shuffle option is real crap, I have 1200 songs on my Watch and sometimes the same song will play twice the same week

121 replies

Jul 18, 2024 9:05 AM in response to hockeybrian

I've griped about this before, but the situation got taken to a whole new level last week. I went to go for a run, fired up my watch, jumped through the "control other devices," scroll through device, "play on other device," "play on Apple Watch" hoops, then paused the music until I could get out the door. In the time it took me to get to the back door, my watch decided that, no, it was going to play music on my phone, not on my watch. I went back to the phone, and there was the music playing. I put the phone in airplane mode, made sure BT and WiFi were turned off, then jumped through the play-on-watch hoops again. Music started. I paused the music. Got to the back porch and hit play. And there it was playing music on my phone again. The only way I could successfully play from my watch to my Shokz was to turn the phone off.


It's bad, but it's not normally this bad. And I will remain completely confused about why I have to click so **** many things to get to "play on Apple watch." When I click the little icon in the upper right corner, it sure seems like "Play on Apple Watch" should be the first thing in the list. They must be convinced that playing on other devices -- TVs, speakers, etc. -- are what people want to do, ignoring those of us who want to use it to run.

Oct 6, 2023 8:50 AM in response to RileyHarder

I just confirmed this (at least the first part). When music is successfully playing on my watch to my non-apple BT headphones, and I hit pause (which I pretty much never do because I use this while running), the instant I hit pause the little icon in the upper right corner of the play screen on the watch switches from showing the three dots with the BT icon, meaning it is playing audio to my headphones from the watch, to the three dots with the little phone icon, meaning it is now controlling my phone. And this means if you do pause from either the screen or your headset, you can't just unpause, you need to go back into the airplay settings described in my first post to restart the music.


Something is seriously wrong.

Dec 3, 2023 9:04 AM in response to hockeybrian

You are amazing, thank you for posting this and letting me know that I'm not crazy!


I've had the exact same experience you're describing. I'd start my music from home on my watch with my phone nearby. When I'd start running and get away from my house and phone, the music would stop and I'd have to interrupt my run to start it again from my watch. This happened whether or not my playlist was downloaded on my watch or not. I'm using Powerbeats Pro for my running headphones.


This didn't happen prior to the WatchOS10 upgrade. I used your workaround this morning and am pleased to report that it worked for me. It's not a "pretty" solution, especially since prior to WatchOS10 it was pretty easy to choose where you want your music to play when starting it from your watch.


Thank you for posting this!

Oct 2, 2023 11:22 AM in response to IdrisSeabright

I am not using or touching the phone at all.

I do have a single playlist loaded onto my watch as I always have since series 3.

When on the watch I go to Listen Now, Library, it shows everything in my iTunes library and when I select something (again, on the watch), even the single playlist on my watch, it starts playing on the phone. I have to then do the dance above listed in my original post, to choose airplay (on the watch) to get to the controls to tell it I actually want to play on the watch, not on my phone.


It is as if with WatchOS10, my watch always defaults to controlling my phone and playing music through my phone unless I tell it to use the watch, EACH and everytime.

Oct 5, 2023 12:27 AM in response to hockeybrian

I'm dealing with the exact same scenario, except for me, it's when I'm in the car driving (as I use a Bluetooth FM transmitter).


On top of having to do the above mentioned steps, I have noticed that if I open the Music app after music is paused for a short while (I'm not sure what exactly causes this), it essentially restarts (like it's the first time I've opened it since I last booted the Watch) and goes right to Listen Now. So I have to hit the back arrow, then Library, then Downloaded, and then find the song I want to play. On watchOS 9 when I opened the Music app, it generally opened to the last album/playlist (or my entire list of downloaded music) from the get-go, unless I restarted my Watch for some reason.


This is an especially bad experience considering, well, I'm in the car, possibly driving, so having to do all of that just to have music downloaded from my Watch play in my car stereo does pose a bit of a safety risk, even if I'm stopped while doing so.

Oct 5, 2023 11:28 AM in response to IdrisSeabright

Something clearly isn't working as intended, unless you're saying Apple intentionally made what is reasonably a widely and frequently used app among the install base more difficult to use.


If the app just remembered what it was doing before without acting like it was just opened for the first time, that would probably satisfy most folks. It was sometimes buggy before, but now it's cumbersome as well.

Oct 6, 2023 9:47 AM in response to hockeybrian

I also just confirmed that if I'm in the middle of my run, far away from my phone, then I can pause and restart music normally. It only seems to be when in range of my phone, the instant I pause playing music from the watch, all controls revert back to controlling the phone as being the primary. And the new UI seems to make it incredibly unobvious/tedious how to start music on the watch if you are also in range of the phone.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

WatchOS 10 makes playing music on watch so much more tedious

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.