My Messages app on my MacBook Air suddenly stopped displaying new messages. Old conversations show, but they have not updated since about a week ago. The problem does not correspond to any updates I performed. The Messages version is 9.2 and the OS is 10.11.4, but this problem started while I was still using 10.11.3.
When I receive a new message, the "new message" icon appears to the left of the dock (so something is reaching the computer), but the message never displays as a conversation in the app. The new message is also not under ~/Library/Messages/Archive.
I can begin new conversations from the Messages app, and replies to those conversations display properly. But conversations not initiated from the app fail to display. Messaging continues to work fine on my iOS devices. It's just the OS X Messages app that doesn't work.
I have tried removing the files com.apple.imessages.bag.plist and com.apple.ids.service.com.apple.madrid.plist from ~/Library/Preferences.
I have also tried deleting the files chat.db, chat.db-shm, and chat.db-wal from ~/Library/Messages. These are recreated as new files upon rebooting, but the problem persists even with fresh DB files.
I also repaired permissions (which in El Capitan apparently needs to be done as a sudo command in Terminal).
When I receive a new message, the "new message" icon appears to the left of the dock (so something is reaching the computer), but the message never displays as a conversation in the app. The new message is also not under ~/Library/Messages/Archive.
I can begin new conversations from the Messages app, and replies to those conversations display properly. But conversations not initiated from the app fail to display. Messaging continues to work fine on my iOS devices. It's just the OS X Messages app that doesn't work.
I have tried removing the files com.apple.imessages.bag.plist and com.apple.ids.service.com.apple.madrid.plist from ~/Library/Preferences.
I have also tried deleting the files chat.db, chat.db-shm, and chat.db-wal from ~/Library/Messages. These are recreated as new files upon rebooting, but the problem persists even with fresh DB files.
I also repaired permissions (which in El Capitan apparently needs to be done as a sudo command in Terminal).