{"id":1392,"date":"2012-09-13T23:39:37","date_gmt":"2012-09-14T04:39:37","guid":{"rendered":"http:\/\/neosmart.net\/blog\/?p=1392"},"modified":"2013-08-26T18:19:05","modified_gmt":"2013-08-26T23:19:05","slug":"os-x-mountain-lion-10-8-2-finally-unifies-imessage-messaging","status":"publish","type":"post","link":"https:\/\/neosmart.net\/blog\/os-x-mountain-lion-10-8-2-finally-unifies-imessage-messaging\/","title":{"rendered":"OS X Mountain Lion 10.8.2 finally unifies iMessage messaging"},"content":{"rendered":"

iMessage fragmentation across devices has been a common complaint ever since iMessage was first released, and although Apple has taken steps to mitigate the issue, it hasn’t yet been truly solved. The problem was exacerbated with the release of Mountain Lion which brought iMessage to the desktop (or to the laptop, depending on what you use), where users of OS X would be allowed to join in the iMessaging fun – but with a very important caveat: the iChat (now\u00a0rechristened “Messages”)\u00a0 messaging software would only register with the iMessage email account, so iMessages sent to your phone number would not be received.<\/p>\n

This meant that users would have to explicitly take care to send and receive<\/em> messages from their iMessage-enabled email addresses; but while you can always select where and how you<\/em> initiate conversations, you can’t very well choose how and where perfectly random strangers will choose to contact you. This limitation also applied to the iPad, however iOS 6 beta seeds included a fix for that, adding the option to initiate and receive messages from the phone number associated with your iMessage account.<\/p>\n

It pleases us to inform you that with Mountain Lion 10.8.2 (as of the latest developer seed, 12C50) this feature has been extended to Messages on OS X, and in the future, your iMessages will be synchronized across all platforms. Here is a screenshot of how your iMessage account looks in iMessage on 10.8.2:<\/p>\n

<\/p>\n

\"\"<\/p>\n

Honestly, there’s no good reason that this was not implemented from the start. In all events, any messages sent from any iDevice go to Apple’s servers where translation from destination number\/email to recipient’s Apple ID is performed. Adding phone number ID support on iPad and OS X requires no number verification as that has already been done on the iPhone. In fact, the na\u00efve solution would automatically result in everything working synchronously and with unified messaging across all platforms. Oh well – all is well that ends well, I suppose.<\/p>\n

The first time you run Messages on 10.8.2 (assuming you’ve already added your iMessage account previously), you’ll be prompted to accept the automated addition\/import of your phone number into your account – you don’t have to do anything manually. Apple’s pulled it from their servers (told you they could!) and you just have to click next. The Messages accounts dialog will pop up and you’ll be asked to confirm your Apple ID password, and then you’re all set.<\/p>\n

Note that your account will be reconfigured to both initiate new conversations from your phone number and to identify outgoing messages as coming from your phone number, regardless of your previous setting (you’ll be asked to confirm this change). With the unified messaging, this is now the most sane option (unless you wish to hide your phone number from people you’re iMessaging), and we recommend you keep it.<\/p>\n

Happy iMessaging!<\/p>\n

Follow NeoSmart Technologies on twitter @neosmart<\/a>\u00a0or follow the author @mqudsi<\/a>!<\/small><\/p>\n","protected":false},"excerpt":{"rendered":"

iMessage fragmentation across devices has been a common complaint ever since iMessage was first released, and although Apple has taken steps to mitigate the issue, it hasn’t yet been truly solved. The problem was exacerbated with the release of Mountain … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":505,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[107,339,846,847,844,845,718,843,350],"class_list":["post-1392","post","type-post","status-publish","format-standard","hentry","category-software","tag-apple","tag-beta","tag-chat","tag-ichat","tag-imessage","tag-ios","tag-ipad","tag-messaging","tag-os-x"],"aioseo_notices":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p4xDa-ms","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/posts\/1392","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/users\/505"}],"replies":[{"embeddable":true,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/comments?post=1392"}],"version-history":[{"count":7,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/posts\/1392\/revisions"}],"predecessor-version":[{"id":2596,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/posts\/1392\/revisions\/2596"}],"wp:attachment":[{"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/media?parent=1392"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/categories?post=1392"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/tags?post=1392"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}