Skip to main content
Question

CarPlay Safety Issue: Playback Requires Interaction with iPhone

  • May 31, 2026
  • 2 replies
  • 12 views

There is a significant usability and safety issue with the iOS + CarPlay experience.

When a track fails to load (whether due to a network issue, unavailable content, or a server-side error), Deezer displays a blocking dialog on the iPhone that requires the user to tap "Retry" before playback can continue.

This behavior is particularly problematic when using CarPlay. The user may be driving and unable to safely interact with their phone, leaving playback permanently interrupted until the dialog is dismissed.

A music application should handle these failures automatically. For example, it could retry in the background, skip to the next track, or continue playback once connectivity is restored. Any of these approaches would provide a better user experience than requiring direct interaction with the phone.

If there is an error that requires user attention, the CarPlay interface should also reflect what is happening. Currently, the issue appears on the phone while the car display provides little or no indication of the problem, making it difficult to understand why playback has stopped.

At a minimum, the app should avoid presenting blocking dialogs on the handset while CarPlay is active, as this defeats the purpose of a hands-free in-car experience.

2 replies

awesomemac
Superuser
Forum|alt.badge.img+9
  • Superuser
  • May 31, 2026

I’ve also had Deezer stop working three times over the past month. In CarPlay I just got a black screen and couldn’t get Deezer to respond at all.

The error message only appeared on the phone, but of course it’s dangerous to pick up your phone while driving and I’m not even talking about the fine you risk if you get caught doing that.

So yes, it would definitely be better if the error message appeared directly in CarPlay, with the option to dismiss it from there.


Jaime.Deezer
Community Manager
Forum|alt.badge.img+7
  • Community Manager
  • June 2, 2026

Hi ​@awesomemac ​@mirswith thanks for reporting this. I’ve passed your feedback to the correspondent team and they are already working on improvements or future updates. 
I can’t guarantee if there will be a fix anytime soon but hopefully it will.
Thanks for your patience and understanding.