Skip to content
iMessage not longer working when using Viscosity on macOS Sequoia
Got a problem with Viscosity or need help? Ask here!
Hi,
After upgrading to macOS Sequoia, iMessage (and maybe other services) not longer working when routing all traffic through Viscosity(tested latest stable and beta).
Guess this is not related to Viscosity but would like to see if others have the same issues and maybe some workarounds.
After upgrading to macOS Sequoia, iMessage (and maybe other services) not longer working when routing all traffic through Viscosity(tested latest stable and beta).
Guess this is not related to Viscosity but would like to see if others have the same issues and maybe some workarounds.
Hi dooh,
We can confirm we can see the same behaviour, and it appears to be affecting basically all VPN applications that route all network traffic. It seems to be a bug in Messages: it doesn't appear to be properly assessing the routing table when assessing network reachability.
We're seeing if we can come up with a workaround, however it's likely something that Apple will need to fix. Be sure to report a Bug Report to Apple, as the more people that report it the sooner they'll likely address it:
https://www.apple.com/feedback/macos/
Cheers,
James
We can confirm we can see the same behaviour, and it appears to be affecting basically all VPN applications that route all network traffic. It seems to be a bug in Messages: it doesn't appear to be properly assessing the routing table when assessing network reachability.
We're seeing if we can come up with a workaround, however it's likely something that Apple will need to fix. Be sure to report a Bug Report to Apple, as the more people that report it the sooner they'll likely address it:
https://www.apple.com/feedback/macos/
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Bluesky: https://bsky.app/profile/sparklabs.com
Support: https://www.sparklabs.com/support
Bluesky: https://bsky.app/profile/sparklabs.com
I thought I was going crazy when this started happening after I upgraded to MacOS Sequoia. I'm glad I came to the forums and there is confirmation that this is a known issue. Hopefully it'll be something Apple can address soon, because it is very annoying!
3 posts
Page 1 of 1