Apple released an update to macOS High Sierra with several notable features on September 25th. Shortly after the update was released, users began reporting various issues and bugs on Apple's support forums, with the numbers growing exponentially each day. For details, refer to: What's New in macOS High Sierra 10.13
macOS High Sierra 10.13 glitch causing delays in sending iMessage and SMS
Some users have reported encountering an issue with macOS High Sierra 10.13 causing delays in sending iMessage and SMS. On devices like iPhone, iPad, and Apple Watch, there's no notification sound for iMessage and SMS. Messages sent are displayed immediately on iOS devices, but on macOS, it may take a few minutes, or even hours, to receive them.
According to user reports, since upgrading to macOS High Sierra, message reception on Mac has been notably slow. Messages are sent instantly on iPhone without notification sound, but on Mac, receiving messages takes a considerably longer time. I'm unsure what issue macOS High Sierra is facing.
Users receive messages hours after they were sent.
Users report receiving messages hours after they were sent. Clearly, this is a downside and something other users should consider when contemplating upgrading their Macs.
Currently, Apple has not shown any initiative to address and fix this macOS issue. However, affected users can apply some temporary solutions to mitigate the problem.
The first solution for users who have downloaded and installed macOS 10.13 is to completely disable message reception, or they can choose to downgrade to macOS Sierra. Other additional solutions include sending messages directly on Mac or disabling and re-enabling iMessage. However, these are only temporary solutions, as the issue may reoccur later.
It seems that in the release of macOS High Sierra 10.13.1 Beta 3, this issue has not been resolved. Hopefully, Apple will soon find a way to address the macOS High Sierra 10.13 bug causing delays in sending iMessage and SMS, or will soon release macOS High Sierra 10.13.1 version later this fall, which includes a fix for this issue.
