Since I updated my Apple iPhone 14 Pro Max to iOS 17.4, I can no longer control the audio playback from my Apple Watch Series 2 with the Now Playing app.
Apple Watch Series 2 | Apple iPhone 14 Pro Max |
---|---|
Model A1758 | Model A2894 |
watchOS 6.3 |
iOS 17.5 iOS 17.6 iOS 17.7 iOS 18.0 iOS 18.2 β |
14 Dec 2020 | 07 Mar 2024 |
The Now Playing app should let you control audio playback on Apple Watch, iPhone, and other devices.
Since March 7th, 2024, the Now Playing app on my Apple Watch Series 2 displays an endless spinning wheel demonstrating that it cannot connect to my iPhone 14.
Failed Troubleshooting Attempts π
- Switching off the Apple Watch Series 2 and the Apple iPhone 14 Pro Max did not solve the problem.
- Forcing the Now Playing app to quit did not solve the problem.
- Toggling the Auto-Launch Audio Apps option OFF and then back ON, in the Watch app on the iPhone, under Settings > General > Wake Screen did not solve the problem.
- Deleting and re-installing the Now Playing app did not solve the problem.
- Unpairing the Apple Watch Series 2 and restoring it to its factory settings did not solve the problem.
Some Online Bug Reports π
- Now playing on Apple Watch not working after update
- Apple Watchβs Now Playing Issue
- Now Playing State Not Updating on Apple Watch
- Apple watch crown does not regulate volume in Now Playing after update
- Now playing Apple Watch 3 series not working after watchos 5 update. What to do?
- Now playing on Apple Watch not working after update
- "Now Playing" App Not Working on Apple Watch
- βNow playingβ not working
- My Apple Watch running watchOS 6.3 no longer displays my iPhone in the 'Now Playing'
- Now Playing app stopped working on Apple Watch β after upgrading iPhone to iOS 17.4 βοΈ
- iOS 17.4: Now Playing not working on Apple Watch
Update March 21, 2024
The release of iOS 17.4.1 on March 21, 2024 did not solve the problem π π»
Update May 13, 2024
The release of iOS 17.5 on May 13, 2024 did not solve the problem π π»
...
Update December 12, 2024
The release of iOS 18.2 on December 12, 2024 solved the problem 279 days after initial report β
Top comments (0)