Was hoping Beta 3 would fix this, but still cant send or receive messages while connected to a VPN. I think it may be related to the iCloud issue others on here have mentioned. Anyone experiencing the same or know of a workaround?
I noticed this too on Beta 2, but no workaround. I just learned to grab my phone if I’m connected to VPN on the Macbook.
Not working for me either on db3. Enabled split tunneling to exclude Messages.app from Mullvad’s split tunneling beta feature on macOS but that didn’t help. Little Snitch shows no network activitiy when messages are being sent, even with the VPN off, funnily enough. Meaning there’s probalby some process sending all the messages, not Messages.app itself.
Edit: It looks like even with the VPN disabled, the behavior of sending messages is very unpredictable. I can send 10 messages, but then afterwards it just stops sending those messages until many minutes later. Even though I can receive messages, the ones I send out aren’t delivered. They only get delivered if I wait 5 to 10 minutes. All in all, this behavior is just really unpredictable, and I highly think it is a bug that needs to be looked at.
Edit 2: tried allowing aspd located at /System/Library/PrivateFrameworks/ApplePushService.framework/apsd as apparently that’s what sends/receives messages, according to my network traffic analysis (I might be wrong here). But that didn’t help, RIP
I’m seeing the same thing with the public beta - hoping this gets fixed. I’ve been using Mullvad for years as well, and with no problems with previous macOS versions.
Just tested and I can both send and receive messages while connected to my university VPN. This is an all traffic VPN, to be clear.
Do you have a whitelist option like IP Vanish has? You could white list Apple.com and iCloud.com maybe
I’m having the same issues on Macos 15.1 beta (i wanted to try apple intelligence lol) and I decided to just use the Wireguard app to connect to my favorite servers and it works with messages! I think it depends on if I connect to it right after starting up
I’m also using Mullvad beta and tried split tunneling unsuccessfully. If you ever figure out a workaround before this is officially addressed/fixed, please drop a line!
I think it depends on if I connect to it right after starting up
What do you mean by this?
Okay I set up the Wireguard app. It didn’t work the first time, but the second time it seemed to work fine. So hopefully it stays this way. I think I can stay on Wireguard until this long-standing issue is fixed. Worth having iMessage back if anything.
Update: Not fixed with MacOS 15.1 Beta
I’ll just downgrade cause I dont really have time for this
For sure will do, although right now I’m just waiting for Apple to hopefully fix this issue in a future beta.