Why is Messages so incredibly awful?
But seriously. Allow me to elaborate:
Messages cannot order messages according to timestamp to save its life. I ONLY use my phone number to send and receive messages on BOTH my iPhone and on my desktop. I don't use an email address or anything else. I have deactived/reactivated iMessage on my iPhone as well as deactiveated/reactivated my Messages account on my computer in hopes of resolving the issue. It was not resolved.
Usually, if my computer and iPhone are both powered on and connected to the internet, my iMessages sync up beautifully. If I send a message on my iPhone, it shows it as my last message sent on my desktop (and vice versa). The same is true if I receive a message on my iPhone.
However, when my computer is offline, all **** breaks loose. For example, I will use my iPhone throughout the day to send/receive iMessages while my computer is shut OFF. At the end of the day, I will turn on my computer and open the Messages app. The app will place some messages (that I sent/received earlier that day) in the middle of conversations that occurred last week (why?!). Sometimes I cannot even find my messages in the application, but this could really just be because it placed them in some obscure location within a previous conversation. The strangest part about these out-of-order messages is that they are TIMESTAMPED all correctly, so I cannot figure out why the app is just placing them in a random order. If I send or receive a photo during the day, Messages almost ALWAYS puts the photo as the most recent message in the coversation (even if it wasn't). Oh, and Messages frequently says I have unread messages, but here's the catch: I don't. Sometimes it will even be bold enough to say that I have "–1" messages. That's probably the most amusing flaw.
This is the most flawed piece of Apple software I have ever witnessed. It renders the app completely useless at looking at past conversations because they are so awfully out of order. Further, this problem has been around since Mountain Lion was released. Is Apple just going to sit by and let this bug continue?
Any advice is appreciated.
MacBook Pro (13-inch Early 2011), OS X Mountain Lion (10.8.1)