10.12.2 "Text Forwarding" & "calls on other devices" not working

I'm not able to get "Text Forwarding" & "calls on other devices" working with my iPhone 6 (iOS 10.2) and new MacBook Pro running 10.12.2.


this all worked fine with my previous MacBook (unibody 2008 10.11.x)


I've tried signing out of messages and FaceTime on the Mac and iPhone, restarting both machines, signing back in on the iPhone then Mac, checking, reloading both and checking again. connected to the same wifi network obviously using the same iCloud account.


when I turn the slider for text forwarding on the iPhone, it asks for a code but the Macbook pro never shows me a code.

when I turn the slider on iPhone for calls on other devices, I get asked for a code and a code is shown on the Mac which I enter, I then see my call history appear in FaceTime but when I initiate a call from MacBook utilising iPhone a call is not placed and no changes seen on iPhone.


calls and messages work fine through my iPad, and I can turn off and on the handoff from the iPhone see the codes on iPad enter and all works as expected.


Anyone any clues as to how to fix this?

Posted on Dec 15, 2016 2:41 PM

Reply
12 replies

Dec 16, 2016 12:40 PM in response to chris-topher

HI,


Just to check.

Apple ID need to be the same on both devices.

iPhone needs the WiFi settings to be set to the same LAN as the Mac.

The Text Forwarding can be enabled and the Code Number should appear.


If it is not reset everything by Signing Out of the Apple ID on both devices, then Closing the App on the iPhone before restarting it and waiting for the number to Verify.


Then Send an iMessages from the iPhone as a test (Manually enter your Apple ID).


Add back the Apple ID.

Reset Wifi if required then Enable Text Forwarding.




User uploaded file

8:40 pm Friday; December 16, 2016


 iMac 2.5Ghz i5 2011 (Sierra)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
 iPhone 6 iOS 10.x and an iPad (2)

Dec 16, 2016 1:01 PM in response to Ralph-Johns-UK

Thanks for replying Ralph,


as mentioned in my original post I already did all those things you suggest & yes same iCloud account and same wifi network. I never get the pop up on the Mac with the code to enter on the iPhone when turning on text forward, in addition "calls on other devices" does not work on the MacBook Pro even though it does pop up a code and the iPhone accepts it, yet the MacBook does n to ring and I can't initiate a call from it.


when I turn the slider for text forwarding on the iPhone, it asks for a code but the Macbook pro never shows me a code.

when I turn the slider on iPhone for calls on other devices, I get asked for a code and a code is shown on the Mac which I enter, I then see my call history appear in FaceTime but when I initiate a call from MacBook utilising iPhone a call is not placed and no changes seen on iPhone.


calls and messages work fine through my iPad, and I can turn off and on the handoff from the iPhone see the codes on iPad enter and all works as expected.


Any other suggestions?

Dec 18, 2016 10:58 AM in response to chris-topher

Hi,


On the iPhone check that the your own iPhone number is not blocked.

In later versions of the macOS and the iOS the My Card in the Contacts app is not called when you try and enter to enter your own name.


I would also do a NVRAM reset on the Mac.

How to reset NVRAM on your Mac - Apple Support


If there happen to be two routers on your LAN then the two devices in question need to be in the same part


User uploaded file

6:58 pm Sunday; December 18, 2016


 iMac 2.5Ghz i5 2011 (Sierra)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
 iPhone 6 iOS 10.x and an iPad (2)

Dec 18, 2016 3:04 PM in response to Ralph-Johns-UK

Thanks Ralph,


only 1 number blocked that isn't mine which I removed, I'm on the same wifi network, I didn't do nvram reset, didn't see how that could affect iMessage, have done now and no change.

in addition I've signed out of iCloud on the Macbook and iPhone & iMessage on both devices too, restarted both and signed into iCloud and iMessage on both with no change, I'm not even able to send iMessages from the MacBook, which if I understand it correctly I should be able to once logged into imessage.


interesting observations:

turning on text message forwarding on iPhone for the MacBook, I'm not prompted to enter a code that should pop up on the MacBook, turning on forwarding to the iPad I get prompted to enter the code that pops up on the iPad.

Now the slider for the MacBook in text forwarding menu does not go to the off position, just pings to on showing the green. I'm able to toggle the iPad, having to enter the code each time I turn it on.


I created a new iCloud account, signed into iMessage with the new account on both iPhone and MacBook, ensured text message forwarding is on, still not prompted for a code and still not able to send iMessages on MacBook & don't see iMessages I can send from iPhone on MacBook.


I had assumed there was something screwy with my iMessage account, but problems persist even with a new account.

Dec 19, 2016 11:47 AM in response to chris-topher

Hi,


There are circumstances where the Mac that is involved is not logged in despite all appearances to being so in the app itself.


If that is the case there are normally three ways it tells you.

1) the App says when you Sign In or Enable the account that it cannot log in.

2) On trying to select anyone by Name in the "To" spot of a New Message they go Red and Say "Not Registered with iMessage"

3) You get to as far as the Send point when the individual message says "Not Delivered" with an Exclamation Mark next to it.


The Serial Number of any device is used to provide a Device specific login so this should be checked first.

If this is missing it will stop any Apple ID from logging in.


Use the Apple Icon Menu > About this Mac item.

In the panel that appears the Serial Number should be the last thing listed in the Overview tab.


if the account is not logged in then the link for Text Forwarding will not work and the Code Number will not appear.


If the Serial number is missing (or does not match the one on the back/bottom or in the battery compartment) then it needs to be replaced at a Apple Store (Or Apple Authorised Service Provider (AASP).).







User uploaded file

7:47 pm Monday; December 19, 2016


 iMac 2.5Ghz i5 2011 (Sierra)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
 iPhone 6 iOS 10.x and an iPad (2)

Dec 19, 2016 1:58 PM in response to Ralph-Johns-UK

Thanks Ralph,


1) both the MacBook iMessage and iPhone iMessage show I'm logged in and MacBook has enable this account ticked.

2) nothing goes red when I select a contact or key in the number for an iphone, the number resolves to a contact and goes light blue.

3) yes I click send and then there is an exclamation mark and the words "Not Delivered"


I don't know if they removed this feature but I'm not able to login to the MacBook with an iCloud account.


I had hopped signing into a new iCloud account and iMessage account would reset iMessage but still something funky going on here.

Dec 20, 2016 11:26 AM in response to chris-topher

Hi,


So Serial Number present.

No Luck with a different ID.

And with the regular Mac User Account the normal Apple ID appears to be logged in but is not delivering anything.


There is one "fix".

It takes longer to describe than the final step in the process.

However getting to that final step can be an fraught experience as well.


Basically you have an apple ID issue but with only one sever (iMessages) and due to the nature of the Device Specific Login it will appears as if only one device is effected.


Call Apple Support (Apple care).

Apple ID issues are free to fix.

However the Level 1 responders are there to solve simple problems under Apple Care fro at least the first 90 days.

This can mean they may not consider Apple ID issues at the first thing.


You are likely to have to ask to speak to someone higher.

Level 2s don't always know about the issue but some do.

It needs them to check the iMessages server and see if it is blocking the use of your Apple ID in relation to your Mac.


Apple know there is an issue and are trying to find out what causes it.

It effects a really low number of people in reality but they have all sorts of Mac models in all sorts of situation so at present there does not seem to be an obvious cause.


They are likely to ask if you have done certain things and want you to try others.

You have to make a decision on how much time you invest in this against getting the actual fix done.


NOTE a Reinstall will not fix this.


Once they have looked at the server and seen your ID is blocked for your Mac you need to ask them to reset it.

Most of the recent responses where people have come back to lets us know what happened this is now being passed to the Engineers.

They can then tell you it will take between 24 hours and 5 days to fix and sat they will call you back.

Most people writing back say they never get the call but the iMessages accounts starts working before the end of the time stated.


Summary.

Call Apple Support.

Be polite.

Insist they look at the Server logins.

Insist they fix it soonest.

Do NOT Reinstall to fix this.

Limit the amount on testing and Data gathering they might ask you to do.





User uploaded file

7:26 pm Tuesday; December 20, 2016


 iMac 2.5Ghz i5 2011 (Sierra)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
 iPhone 6 iOS 10.x and an iPad (2)

Dec 23, 2016 2:18 PM in response to chris-topher

That was painful.


i did phone apple and my iMessage / iCloud account was fine we did a number of troubleshooting steps in the ~2 hours i was on the phone and the agent viewing my desktop over remote assistance.


highlights:

deleting message and ichat preferences and other files from ~/Library/ got me to a point where i was unable to sign in or out of iMessage, preferences->accounts showed my iCloud account in left pain sometimes stating inactive sometimes enabled


reseting keychain had no effect


i created a new account on my mac and signed into iMessage on that and was able to send and receive iMessages, i was still not able to sign out of iMessage, the preferences->accounts dialogue just showed the iMessage account in the left pane with no additional info on the right pane.


i created another new account on my mac and signed into a different iCloud account in iMessage i was still unable to sign out of iMessage, the preferences->accounts dialogue just showed the iMessage account in the left pane with no additional info on the right pane again. the login keychain was empty before i opened iMessage.


i have no idea what was causing iMessage to not show any additional attributes for the iMessage account. resetting the login keychain, deleting caches and any and everything in ~Library/ and /Library/ to do with ichat/iMessage, disk first aid and reboot did not restore the ability to logout of iMessage


Apple support recommended i created a new account and copy my info across but that still left iMessage in the same funky state as above.


in the end i booted in disk utility mode, erased the ssd, reinstalled os x, and used migration assistant to copy my data again from my old macbook ssd (usb-c -> sata 3 cable) 200GB copied in ~1hour.


i've now got all the old crap (prefs, kexts etc) from my 2008 unibody MacBook (running El Capitan) that i was hoping to leave behind but at least my new machine is now running how i expected it to be.


The final apple support recommendation of creating a new account wasn't enough to solve this. There is a file somewhere in /Library/ that was causing this undesired behaviour but i was unable to find it.

I wish apple published a list of files their inbuilt apps where dependant on, would have saved a whole bunch of time. Also keychain first aid would have been helpful, to rule keychain out of the possible problems.


i hope this info helps someone.

Dec 24, 2016 1:27 PM in response to chris-topher

Hi,


.plists

Anything containing "iChat"

Some are less important as deleting them changes nothing about logging in.

For instance the com.apple.iChat.StatusMessages.plist only hold the most recent Status Messages you have set in Account that Have buddy Lists (AIM, Jabber.Yahoo and Bonjour i.e. nothing for iMessages.)

You might see a LSSharedFile one which is now useless as you no longer have the Menu item for it. It holds a list of the most Recent Chats. (it used to be in the File Menu). How many is controlled in System Preferences > General along with the setting for Recent Severs and Apps. (the "Documents" refers to the Saved items of Any app).


The com.apple.iChat.AIM( or Jabber or Yahoo or Subnet).plist refer to the Buddy List accounts you may have started up.

Jabber includes Google. AIM includes some Apple ID names (you add them as if they are AIM but use the regular password as AIM and Apple have an Agreement that their ID will be recognised an AIM Screen Names).


Deleting the actual com.apple.iChat.plist can help if the issue is with the Preferences and some Menu item Settings (Mainly Sorting Buddies and Chats)


com.apple.imagent.plist effectively logs in the accounts in behind the scenes when you start up the computer and provides a listening service to the various servers for Off Line Messaging.

If it sees a chat item it will start up the app (unless you set the item in the General section of the Preferences about setting the Status to Off Line when Quit)

This item only works for Accounts with Buddy Lists.

iMessages ignores this and still places number on the Dock badge but does not start up the App.

This is because as you have found out the iMessage account has no Status.

Deleting this .plist tends only to work with the Buddy List accounts.


User uploaded file


com.apple.ids.service.com.apple.madrid.plist holds the Apple ID and the Alternatives you may have linked to it (iPhone Number(s) and other emails).


The com.apple.imessages.bag.plist only hold the server you were last connected to.


The com.apple.imessage.plist holds info about whether the default font has been chosen for Previews and the Font for the text has been chosen.


There are then some in ~/Library/Containers/com.apple.soagent/Data/Library/Messages

You have some here that have "messageshelper" in the names.


User uploaded file


Most of the info though is about Buddy Lists Accounts.


Back in /Library/Preferences and just below the madrid one there are many IDS items relating to the links between iPhone and Mac for both messages and the FaceTime app, depending how and which functions that are connected for.


Keychain Access will show you an IDS: yourAppleID-Auth Token This may have to be removed if the Migration has copied across one from another Mac.

It is this bit that holds the info used based on it's creation by having the Mac's Serial Number. That is to say that the ID and Password and the Serial Number are used to help create this token when logging in the first time.

Migrating the Keychain from another Mac brings a token with the wrong Serial Number in effect.



User uploaded file

9:27 pm Saturday; December 24, 2016


 iMac 2.5Ghz i5 2011 (Sierra)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
 iPhone 6 iOS 10.x and an iPad (2)

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

10.12.2 "Text Forwarding" & "calls on other devices" not working

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.