An internal Messages error occurred. (tried everything)

This occurred when I upgraded to Mojave. Given that I have not seen similar Mojave-related complaints, but have also seen complaints about this with previous OSs I am gonna assume this isn't a problem specific to Mojave, but not sure.

Nearly every time I open Messages I get the error pictured below "An internal Messages error occurred. There was a problem with Messages. You need to quit and open Messages again."

I can usually get it to open if I go through this a couple times. But once I'm in messages, my conversations (which are synced to iCloud Messages) are not shown the same as on the phone. Commonly I will receive a message on my phone along with a notification on my Mac, but when I click it on the Mac, the conversation doesn't open in Messages, and I can't find it in the list.

I have deleted every iMessage preference file indicated on other forums, deleted library/messages, signed out of messages completely, disabled and re-enabled messages in the cloud on both my iPhone and Mac, and cleared my PRam for the heck of it.

Please send a (working) iMessage from the heavens and tell me what to do!!

2017 MacBook Pro 13" w Touch Bar, Mac OS Mojave 10.14.

User uploaded file

MacBook Pro TouchBar and Touch ID, macOS Mojave (10.14)

Posted on Sep 26, 2018 9:42 AM

Reply
Question marked as Top-ranking reply

Posted on Sep 26, 2018 9:51 AM

Hi,


A Safe Mode boot deletes system caches that can help after a macOS update or upgrade.



To start up in safe mode:


  1. Start or restart your Mac, then immediately press and hold the Shift key. The Apple logo appears on your display. If you don't see the Apple logo, learn what to do.
  2. Release the Shift key when you see the login window. If your startup disk is encrypted with FileVault.


To leave safe mode, restart your Mac without pressing any keys during startup.


Hopefully the internal message won’t appear.



Use safe mode to isolate issues with your Mac - Apple Support

109 replies

Nov 15, 2018 11:15 PM in response to dantaylr

Every single mac I have with 10.14.x have this issue after I once pressed "sync with icloud". It worked perfectly until pressing the sync button.

Since I have it magically across every single mac, this should be a macOS bug and Tim does not care.


To replicate the bug (for any caring Apple engineers). 10.14 + messages in the cloud + press the sync button in macOS.


I guess that less than 1% of macOS users have messages in the cloud + press the sync button = why nobody seems to care that this does not work. Messages are such a huge mess. (and explaining it is maybe of the topic, but a simple example. I use my @mac address as imessage. I bought a new iPhone and moved the SIM from my old = My phone number is unregistered as messages device and the new phone have to be activated for messages. Now my default messages address is switched from @mac to my phone number. Problem? Well, using different sent addresses creates different messages threads. And since Tim randomly thinks its fun to alter my sent "from" address I have at least 5 different sent aliases at my friends. Yes: newer iOS/Macs should merge those threads, but that does not work.

Nov 15, 2018 11:35 PM in response to dantaylr

Its funny how many religious help answers there is in this thread.

Log out/log in from messages. (classic Windows solution)

Reboot the device.
Use DiskUtility. (maybe Apple should use a better file system? Especially people using HSF+: surveys show that 90% of the users have rights errors that are created by the file system). macOS is Unix. The best OS in the world that is used on all high-end servers/mission critical stuff. Rights issues on file system should not exist and have been addressed a bit by APFS. (even if Apple forgot read/write verification).


This issue is activated by pressing "sync with icloud" = the whole point with messages in the cloud. (and every single Mac user I know moved their messages to iCloud to fix the simple issue that Apple cant propagate the same data to users with many Apple devices. The desperate theory is that if it's on the cloud= at least syncing this data should be easy. And every single one of these users pays for extra iCloud space, so messages in the cloud is a pay service that does not work.


I have no idea how to solve this problem. If I log out/in messages macOS. Tim thinks I only have SMS messages, every single imessage thread is gone. If I write to a user with messages, that thread is activated when the messages are sent. So I could try to send a message to every single person I sent a message to the last 5 years to repopulate the list. But... Tim thinks that is bad since when I quit messages and start it again he forgets all threads.


diskutil, log in/out. Read backups from TimeCapsule. Play with the lib folder. Reset PRAM. Pray to Tim. Nothing worked. heck.. Maybe I should threaten macOS that I will install Windows over it... oh... Tim has removed bootcamp in 10.14 = why that threat does not work.


How hard is it to sync data peer to peer? If I have 5 Apple devices: why can't they have the same messages data? iSync managed this and solved sync issues by asking the user what version should be saved (and making it easy for customers is one of the reasons why this does not work today. Sync conflicts aren't solved)


Since all macOS 10.14 machines are affected: how can it be a local error?

And it works on 10.13 machine that I have not upgraded yet. So maybe someone at Apple should fix this? Be a hero to its users that love their products because "they work"? (I miss Steve. When @me launched and you could not log in the first day: he summoned the cloud team in the auditorium. Took the boss to the stage. Said: You have failed each one of them (engineers/customers) and fired him. As a user, I got 2 years free @me just because of slow logins.

With Tim and the disaster iCloud/macOS: They can do anything. Manhandle the users. And nothing never happens since it works for Tim. Tim has a local icloud server hub under his desk with 10Gbps dual ethernet. "it works for me". That is today's Apple. Someone should be fired for this messages bug, especially that it was not fixed with 10.14.1

Nov 16, 2018 1:59 PM in response to dantaylr

I think my issue was the same as what many have described.. After I installed Mojave on the iMac, I could not open messages. I just got that box message that said the "An internal Messages error occurred ..." Tried many suggested solutions. For me, it turned out to definitely be an iCloud problem and the solution was to disconnect messages from my iCloud:


1. Open Apple at top left

2. Open System Preferences.

3. Open iCloud.

4. Open "Options" next to "iCloud Drive."

5. Uncheck "Optimize Mac Storage" at bottom of the box and click "Done." (I believe what what I was doing was basically turning off iCloud in my Mac.)

6. Messages opened, including having all my priors.

7. In the topeft of the screen opened Messages to get to its preferences.

8. Opened Preferences.

9. Clicked on the "iMessage" tab near the top left of the box.

10. Unchecked "Enable Messages in iCloud," It allowed me to do this only if I agreed to do it for all my devices and I clicked to allow that to happen and the box unchecked.

11. The went back back to iCloud in system preferences and clicked options next to iCloud Drive, and then checked the box "Optimize Mac Storage." I assume I was reconnecting the Mac to iCloud for most everything except that Messages would not be connected to iCloud.


Messages on the iMac has worked fine since I did that, except that they are undoubtedly not going to iCloud.

Feb 11, 2019 2:31 PM in response to dantaylr

I also have this problem - still have this problem after following all instructions to safe boot and create a new user. Nothing worked so I wiped my HD and reinstalled Mojave. No luck. However now I'm thinking my mistake was using Time Machine to restore after the clean install. Did I just reinstall the problem? Should I have just dragged my non system folders to a HD and not used a backup? It's now 2019 and it doesn't seem like this problem is being addressed by Apple.


Jun 8, 2019 11:51 AM in response to dantaylr

I am also having this issue. Started immediately after upgrading to Mojave. Tried to use Time Machine to go back and the restore fails to ever load and hangs at the apple logo.


It definitely seems to be a cloud issue as I've reproduced most of the scenarios described in this thread, and tied to specific threads and messages. I completely cleared every ichat/message artifact in the OS and started clean...send a couple of tests afterwards, worked fine. As soon as messages sync'd with the cloud, those threads vanished, and the standard "partial" cloud sync (minus the missing threads) showed up.


I'd give anything to be able to go back to High Sierra, but I can't seem to get that to work either. Apple has had my loyalty for a long time as a result of their reliable platform. This issue has been going on so long with no even hint of being addressed...maybe its time to reconsider.

Jun 14, 2019 12:35 PM in response to ahoogerhuis

I've also temporarily fixed it the same way as 99ramon. New messages work just fine with a fresh install, just leave that cloud sync disabled. The second that starts to sync, you're going to be hosed again.


Catalina can't get here soon enough, its really annoying and amazing they've left it so broken and not even acknowledged it for so long, where apparently they knew about it....as they fixed it.

Aug 2, 2019 7:12 AM in response to BlutoForever

While you "have the hood open", take a peek at what's in

/Users/you/Library/LaunchAgents

/Users/you/Library/LaunchDaemons

["Agents" and "Daemons" are nerd talk for background programs)

In that directory (if they exist) are third party app background apps that start when you login. Google their name, and decide if they are helpful. Drag to the Trash if you don't want them running.. This is a common way to


  • Start helpful utilities at the top menu bar
  • Infinitely, quietly run in background looking for updates
    • The com.google.keystone ones look for Google Chrome updates and will always come back if you delete them)


There is.a system wide pair of Launch directories under /LaunchDaemons

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.

An internal Messages error occurred. (tried everything)

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