iOS 13.5 Siri will not open apps while driving

Fermin Bernaus wrote:

iOS 13.6.1 but I do not think the iOS version is relevant anymore. For me, it is clear the apps needed an update to manage this new behaviour.

No, this is entirely a Siri issue. There is nothing in the API documentation (which is public, see https://developer.apple.com/documentation/sirikit) that even allows an app to change how it reacts depending on where Siri Eyes Free and/or DND While Driving are on or off.

I have another theory (or hunch) with what 'broke' Siri when connected to Bluetooth Audio car stereos since iOS 13.5.

iOS 13.5 allowed for unlocking our iPhones with Face ID whilst wearing a mask. As this bug does not affect all iPhone users, I am convinced that there is a feature or setting that some (the vast majority of) iPhone users are using which somehow doesn't invoke the Siri - Do Not Disturb While Driving bug.

For example - I don't use Face ID to unlock my phone or wake it from sleep - I have never set up Face ID on any of my new iPhones and never will. It's not something I care to use. I prefer to unlock my iPhone with my hands and a 4-digit passcode.

As the 'Unlock with Face ID whilst wearing a mask' was such a BIG feature of iOS 13.5 during the first major Covid-19 outbreak - is it possible that something in the Face ID set up or settings is preventing the ability to 'Manually' set Do Not Disturb While Driving?

How many of us in this thread are experiencing the 'Siri - DNDWD' bug who don't have Face ID set up or use Face ID on their iPhones?

If I had to put money on it - this (extremely frustrating) BUG has got something to do with a signal like 'Siri Eyes Free' coming from our car stereos - or it's messed up with Face ID.

Who else has this bug with Face ID turned off?

EDIT: After work today (it's 1pm here in Auckland City, New Zealand) I'm going to completely erase my iPhone 11 (again for the 7th time), and this time set up Face ID during the initialisation set up prompts - and then try connecting it to my car stereo and see what Siri does with Face ID turned on.

I'll definitely report back with my findings.

You might also want to think about a DM to @AppleSupport on Twitter. I've used it in the past - one time - for an issue and they resolved it. I took the liberty of linking to this thread and mentioning you since I think you laid out the issue succinctly in the DM I just sent them. I'll post any response they provide.

Have you given any thought to a clean install - not from backup? Pretty sure when you restore from a backup it also restores a number of settings. I'm thinking about a clean install and seeing if the initial load has the issue. If it does not - then I'd add apps in groups - e.g., financial, travel, etc. and test after each group add.

I've searched about this issue - there are not many of these type complaints. Apple rep asked me to provide logs of when it happens - I did that with them - they will get back next week. These are times when a unique set of conditions initiates an error. In this case I'm guessing we all have that unique set of conditions.

I think the engineer(s) are trying to figure out what those conditions are. They will, and it will be fixed at some stage. iOS is complex - great deal of code - provides a lot of services - extremely hard to account for all the possible permutations and test for them - which is why, in part, they have public betas.

My workaround is to not connect to BT - rather simply use the iPhone speaker -- my iPhone is mounted on the dash - easy for me to do it this way.

In any event, this is not the end of the world - it's just a phone with a problem.

SeeJane and Inkkling, you're exactly right. I and so many of us have contacted Apple about this. I did via Apple Care and was transferred to senior-level support, where I explained in great detail what we all are describing here. To no remedy.

You are correct that the flaw is forcing us to interact with the phone while driving, or be without the services touted by this company when selling the product.

While the "Solved" post offers some very small degree of workaround, it does NOT resolve the problem, and we have told Apple that, here and elsewhere. They certainly should be aware and should have explained the problem to their support staff so they aren't clueless when we reach out.

Our concerns are being ignored.

Needing a resolution, as I WANT TO DRIVE WITHOUT THE DANGERS OF INTERACTING BY HAND with my phone while driving, I have spent significant funds purchasing the new MS Surface Duo. This puts me in the Android camp for my phone for the first time, and I've been Apple iPhone loyal for many years and through many purchases for myself and my family.

I do not want to put us at risk, however, and Apple is tone deaf on this issue. I'm so surprised they would be willing to risk their 22.17% iOS market share.

I know the Android switch to this new phone will not be perfect, but if it meets my objective of hands-free communication (which clearly is what we all want here), then it could protect my loved ones and yours, and it's worth it.

In my humble opinion.

You do realize that complaining in a user forum isn't gonna get Apple's ear. They don't monitor this or take tech support requests from it. If you have an issue with an expected feature on the device, hit contact support at the top of the page, get to a Senior Advisor and file a ticket with engineering. That is the only way they are going to know about the impact it is causing. Simply complaining about it in a user forum will lead you no where.

What you take as an insult is just me pointing something out sir/madam. This is a USER SUPPORT FORUM, you are speaking to other users, not Apple. If you want help with an issue, yes you can and are encouraged to work with other users and contact support as needed, but simply complaining about the issue isn't going to help. I was simply encouraging you to seek assistance where it will make the most impact. If Apple is not aware of the issue, and just complaining in the forum doesn't make them aware, then how are they to fix it. How are they to fix the issue without logs and diagnostics from users experiencing the issue? How do they determine where the fault is without insight from the customer? Just questions I am asking, I am not attempting or intending to insult you in any way.

I drive a 2015 Ford Fiesta. Worked perfectly for me as well until 13.5. It's hard to say whether it's just one manufacterer because it seems other people are having the same issue in this thread that aren't driving a Ford. I can't beleive my next vehicle is going to be based on whether Siri works or not. Seems like a small thing but I feel extremely unsafe doing everything manually now after getting so used to "hands-free". I'd gladly switch to Android, but unfortunately many of us are very connected to the ecosystem. But...the lack of hand's free functionality in my car and the refusal to embrace xCloud (unrelated) might be the straw to break the camel's back.

I'm currently not an active developer, nor I run betas, and it let me log in and report. I have no idea if that's why my ticket has been sitting there unwatched all this time, though.

The problem with AppleCare is that they go through a script and in this case nothing we do works. I'm still surprised that for a while it worked for me, after merely disconnecting and reconnecting Bluetooth.

I'm starting to lose hope about this, to be honest. It doesn't seem to affect enough people for someone in the Siri team to actually look into it, and most people seem content with Apple Maps anyway (which, not surprisingly, is unaffected). Too bad Apple Maps is at best mediocre, compared to other navigation apps, in many places outside of the US.

@jollino Can you try other commands while connected to BT? For example, asking "Where is the closest Starbucks?" Or asking "What's the weather forecast for today?" These are 2 commands I used to use frequently via Siri BT that do not work anymore. Asking Siri for info with variable answers seems to be thing that causes the main issues for me.

For example, previously when I'd ask Siri for the closest Starbucks or McDonalds, Apple maps it would pull up an actual list of various results on the screen and I could tap on the closest recommended or choose a completely different option. Another example, when asking Siri weather conditions it would list the current weather on screen. I've attached images of how it looks when it's NOT connected to bluetooth. Both of these examples do not work anymore for me while connected to vehicle's BT. I get no response from Siri. Just the image with the car and the floating Siri orb.

Yep, that's why I was asking if anyone had actually tried it. :) It's possible it didn't make it into the release notes, like the control center widget for Shazam (which was arguably the biggest new feature of beta3).

The message I got says "As a result of your feedback, there are software changes in the latest update, build 18B5072f, that have resolved this issue. You can see the software build your device is running and check for the latest update by tapping on Settings > General > Software Update."

Yes this happened to me months ago too. I did publish a similar message to yours and I was accused by someone of not being of any help to the community if I was not having the problem ... but it's just the same scenario, it was not working before and I was experiencing the same issue as everyone in this thread but now it is working in exactly the same way as you describe.

Moreover, Spotify is working too. And let me point out: there were like two weeks in which Spotify was suddenly working with Siri when driving but not Waze, then all of a sudden both started working. Not for other apps, but I think that's fair (I should not be opening Chess when driving - ok). And there were no iOS updates in between. So they should have been app updates, otherwise I don't have a clue ...

But since there are still so many people complainig, unless they are not in the latest versions of both iOS, Spotify and Waze there must be something else in the equation that needs be fixed.

Fixed for me! iOS 13.6 became available today, and installing this fixed the problem. Confirming that I can open Spotify and Google maps via Siri.

No, I had previously deleted the connection and re-connected in earlier attempts, but not this time in 13.6.1. I simply turned bluetooth off and then back on.