watchOS 4.0 - Now Playing Stays On Screen

Question

watchOS 4.0 - Now Playing Stays On Screen

Hello all,

After upgrading to WatchOS 4.0, whenever I would play a video on my iPhone's YouTube app my Apple Watch shows the video controls on the face. The iPhone is a 7 Plus with iOS 11.0.1.

Thats fine and all, but when I close the YouTube app, and even swipe the app clear from the background all together, the Now Playing control stays on my Watch face. And its just a play button that does nothing when pressed. I have to press the Watch's crown button to go back to my regular watch face.

This never happened on watchOS 3.x.

Does anyone know of a workaround for this? Or is this just a bug in 4.0?

Apple Watch Series 2, watchOS 4

Posted on Oct 4, 2017 6:07 AM

Reply

Answer 1

Top-ranking reply

Jonathan UK

Level 10

164,015 points

Oct 4, 2017 6:10 AM in response to neverGoingBack

Hi

Now Playing can be configured to be shown automatically on Apple Watch upon raising your wrist when playing supported media on your iPhone.

If you would prefer to turn this feature off:

On your iPhone, in the Watch app, go to: My Watch (tab) > General > Wake Screen > turn off Auto-Launch Audio Apps.

To configure your preferred settings for what is shown on the watch face upon raising your wrist, follow these steps:

On your iPhone, in the Watch app, go to: My Watch (tab) > General > Wake Screen.
Under the heading "On Screen Wake Show Last App", select your preferred behaviour.
- To have the watch face return to the time rather than the last app used upon raising your wrist, select "While In Session".
- Note that session-based apps that are still in session (such as during a workout) will still be shown upon raising your wrist.

Reply

Answer 2

Oct 4, 2017 6:21 AM in response to Jonathan UK

Hello Jonathan,

Thank you for the quick reply.

Yes, I have tried your settings suggestions before. While those do fix the YouTube issue for me, using those suggested settings prevents Apple Music controls from my Watch.

Like I said before, watchOS 3.x did not have these issues, this is why I was asking if watchOS 4.0 is bugged.

Reply