Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Siri: workaround Content Not Available error iOS devices
A few weeks ago, a number of people started reporting having trouble with Siri. Phrases like 'Call my wife' or 'Tell my dad' stopped working. Siri knew who those people were but proclaimed 'Uh oh, I don't have a phone number for Jane Isa Doe." and beneath, there's a message: "Content Not Available."

I debugged this for over an hour and on a hunch, found a workaround that seems to work for nearly everyone who has tried it. All you have to do is delete the middle name of the person in *your* contact card where it is stored as a relationship.

I'm not sure why that works; it shouldn't, but it does. That's why I call it a workaround instead of a fix. I figure Apple is mucking around with Siri and perhaps caused a bug or some sort of corruption.

I'd be curious to know from MacOSXHints users whether they are experiencing this problem in the first place and if the workaround works for you, too. I'd also like to understand why this works and why the problem even exists. I had tried a ton of suggested fixes for the issue before stumbling upon this work around.

You can read more about it in my blog entry. In it, I link to the Apple discussion forums at the bottom, where people have been saying that this workaround fixes the issue for them.

[crarko adds: I find I already don't have middle names in any of my Contacts, so I've not seen this. I wonder if something is going on at Apple's end, where the Siri processing gets done. Perhaps in preparation for iOS 8.]
    •    
  • Currently 2.67 / 5
  You rated: 1 / 5 (9 votes cast)
 
[9,396 views]  

Siri: workaround Content Not Available error | 7 comments | Create New Account
Click here to return to the 'Siri: workaround Content Not Available error' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Siri: workaround Content Not Available error
Authored by: redfood on Sep 11, '14 07:45:27AM

I had this problem. Clearly it was a bug and it probably got taken care of since we had issues.

For me, simply restarting the phone fixed the problem. (A full power down/ power up). My guess is that editing the middle name forced it to re-load the contact info as did my restart.



[ Reply to This | # ]
Siri: workaround Content Not Available error
Authored by: robleach on Sep 11, '14 10:09:53AM

Power cycling didn't fix it for me. In fact, today, I removed and recreated the wife relationship and started getting the "Content Not Available" message again. I deleted the middle name again and it started working again. And for the past week, I've been getting responses on the apple discussion forums thanking me for the fix.



[ Reply to This | # ]
Siri: workaround Content Not Available error
Authored by: mr_yellow on Sep 11, '14 11:15:01AM

OMG... this has been bugging me for the past few weeks... THANK YOU for posting this! I tried deleting the relationship profile, rebooting, turning off and on siri, icloud, and all the variations inbetween. I never thought to edit the names of the people.

I ended up deleting the middle name, creating a new relationship to the middle-name-less profile (I had to remove the old relationship that was still pointing to a profile with the middle name), and tested it and it worked. I then *added* the middle name back into the profile, this automatically created two "spouse" relationships (one with and one without middle name) in my profile. I deleted the relationship to the middle-name-less profile, and I'm back rocking with a middle name in my spouse's contact.



[ Reply to This | # ]
Siri: workaround Content Not Available error
Authored by: robleach on Sep 16, '14 08:05:50AM

I just tried implementing your process to see if I could get it to work, but was unsuccessful. I'm a little unclear about some of the steps though, so maybe I'm not doing it right. First, I re-added my wife's middle name in the spouse relationship in my contact card to go back to the state where Siri doesn't work. Then I tried implementing your process and as soon as I deleted the contact without the middle name, it stopped working again. So, are you starting out by creating a new contact card for your wife with no middle name or are you deleting the middle name from the existing contact card for your wife? I was unclear on that part. Then, did you delete the spouse relationship in your card and then create a middle-name-less one or did you leave the one with the middle name and add a second one to the middle-name-less card (and is that the duplicate or edited original)?



[ Reply to This | # ]
Siri: workaround Content Not Available error
Authored by: SaSaSushi on Sep 11, '14 02:58:04PM

What finally worked for me was not removing any middle names but rather removing all relationships and adding them back in again by their first name only. Bizarrely, this actually worked where nothing else would.



[ Reply to This | # ]
Siri: workaround Content Not Available error
Authored by: robleach on Sep 16, '14 06:25:45AM

Interesting mr_yellow & SaSaSushi. Yes, I think that creating brand new contacts can work. I've heard evidence of this before. My contact cards are chock full of info and would be very laborious to re-create, thus I like mr_yellow's solution which retains the original contact card. I will note here that I did try exporting, deleting, and reimporting both contacts involved in the relationship and that did not work. So either you need to recreate your contacts manually or use mr_yellow's trick to de-corrupt Siri's copy of that card. Of course the simplest yet is still to just delete the middle name of the contact stored as a relationship in *your own* card, however it's not the ideal solution.



[ Reply to This | # ]
Siri: workaround Content Not Available error
Authored by: robleach on Sep 19, '14 07:42:02AM
So I read on one of Apple's discussion forums that someone who called in about this problem to Apple got escalated and started talking to a programmer who is starting to look into this issue. Yay!

[ Reply to This | # ]