Somewhat unrelated - SMS seriously needs to die.Īny phone carrier call center employee can check your inbox, supposedly that's an audited procedure but having worked in a call center I would tell you that I'd believe that nobody's watching anything. MMS take forever and you're lucky if you even get half the messages in a timely fashion in-sequence. Messages get split up over 140 characters. It's hard to appreciate how unreliable, low quality and all around bad SMS/MMS is if you've been using iMessage for a few years. That's probably the shittiest thing about switching.
Though a password change to your Apple ID, or managing the associated phone numbers there should address the issue.īTW, SMS on Android. If you sold the device without a reset you have a lot more to worry about than iMessage I think. That obviously wouldn't happen if you had reset and sold the device. That said, when iOS7 came out, and I logged back into my iPad, and my wife on her iPad Mini, and her iPhone 5, iMessage reenabled on all of them with my phone number. If there's no device actively logged into iMessage, no attempt is made to send through iMessage. That's why you occasionally get the "Send as SMS" prompt if it can't go through for whatever reason. Turn the old phone off and problem solved. iMessage was definitely a pain since I left the (SIM-less) iPhone on at home and my wife's messages went there since it was on the WiFi.
I just swapping my iPhone5 for a MotoX a couple weeks ago.
That shouldn't be possible if the application is just directly talking to Apple the entire time. It then gets back two packets from the Chinese server, the first of which I'm presuming is the decoded result and the second packet being a response to send Apple (as immediately a packet is sent back to Apple with about the same size).Īdditionally, if you read the reviews of this application, the author is making some very weird responses to people with login issues: he's asking for their Apple ID, as apparently that's enough for him to debug their issue.
Here's what I'm seeing: every time I send it a message, I get a packet from Apple, and then immediately the app sends a packet of almost exactly the same size to 222.77.191.206 (which is listed in this application's APK as "ServerIp").
Instead, it ferries the data to the third-party developer's server, parses everything remotely, figures out what to do with the data, and sends everything back to the client decoded along with responses to send back to Apple.ĭoing it this way means that Apple can't just block them by IP address, it avoids them having to distribute their "secret sauce" (understanding the iMessage protocol is clearly very valuable), and it potentially allows them to use actual Apple code on their servers (in case they haven't spent the time to fully break the fairplay obfuscation that Apple is using for some of their keys). I believe that this application actually does connect to Apple's servers from the phone, but it doesn't then interpret the protocol on the device.