Q: Unable to send SMS
I have an Apple Watch running watchOS 2.2.2 (13V604) and an iPhone 5S with iOS 9.3.5 (13G36). Previously, I found that the watch would not send text messages hands-free unless I turned on iMessage; these messages would simply vanish, but all seemed to work well for a few weeks after iMessage was activated.
Now I find that the following will happen if I try to send messages to someone who is not using iMessage (e.g. Android users):
"Hey Siri, send a message to $PERSON saying $MESSAGE" -> within a few seconds a notification pops up showing that the message was not sent. The message does not appear in the messaging app on the iPhone, yet I know have many unsent messages in the watch message app (it seems impossible to re-send or dismiss these). If I select a message manually via the messaging app on the watch (either by replying or composing a new one) then it is sent correctly.
Unfortunately, sending hands-free text messages to Android users is very high on the list of essential requirements for using this watch. Can anyone suggest how to deal with this? N.B. I have already turned iMessage off and on again and power cycled both watch and iPhone.
Posted on Sep 1, 2016 2:34 AM
Thanks for all the replies!
The shop (not an Apple Store, but a reseller) were of no use, stating that I'd have to wipe the iPhone and discard my backups. Not only would this have been a pain but it would not have fixed the issue as it was caused by my contacts information and would have reappeared once the contacts synced to the iPhone.
The problem turned out to be that several of my contacts have two entries; one, with the phone number, I added manually and another with the email address only which seems to have been added by Google+. Initially Siri was using the entry with the phone number but seems instead to have been finding the entry with only an email address for the past few days. As most of my contacts use Android there would be no iMessage account associated with that address and no message could therefore be sent (perhaps a more detailed error message would have helped here).
Anyway, perhaps this might be of use in case anyone else encounters the same problem.
Posted on Sep 2, 2016 11:01 AM