#335 "Voice calling / video calling is not supported on this browser" message.

[Anonymous]

Originally created by: HomeStarRunnerTron

I'm surprised I don't see this in the Issues, which makes me wonder if it's just me... I can't make any Voice or Video Calls! I'm an ARM MacBook running macOS 15.7.5, if that helps...

In most cases, the buttons to call are just greyed out and read as follows:

The ones that aren't greyed out (for what reason, I don't know) give me back a message like this when I click them:

(Clicking Install Chrome does nothing, as expected.)

All the best, hope you have a wonderful day & beyond!

[Anonymous]

Originally posted by: kristofferR

@HomeStarRunnerTron - Thanks for the report, this should be fixed in 2.0.7. 🙂

Can you test it and report back?

[Anonymous]

Originally posted by: HomeStarRunnerTron

Actually, it's still exactly the same behaviour as before for voice & video calls! I had to log in from scratch, and I deleted all my preferences for a clean install, as far as I know. Thank you so much for taking a look! : )

[Anonymous]

Originally posted by: kristofferR

@HomeStarRunnerTron Whoops, my mistake, fix was insufficient. How does version 2.1.0 work?

[Anonymous]

Originally posted by: HomeStarRunnerTron

@HomeStarRunnerTron Whoops, my mistake, fix was insufficient. How does version 2.1.0 work?

I don't know if it's something about the whole restoring PIN process, or what -- I tried relaunching after the initial restore, but I'm still getting grey de-activated call buttons.

This is a completely separate issue, but while I'm here, Carrier handles the login window a little oddly.

Light Mode (funny scrollbar window in a scrollbar window for no reason):

Dark Mode (same issue, plus fonts aren't displaying changing colors to match the rest of the theme):

[Anonymous]

Originally posted by: kristofferR

[!NOTE]
🤖 Claude Opus 5.5 responding on behalf of Kristoffer, comment manually approved

Thanks for testing 2.1.0, and sorry it still isn't working. 2.1.0 fixed calls failing to open their window, but your screenshot shows Messenger still rejects the browser before it gets that far. I can't reproduce this on a newer macOS, so could you help with two things?

1. Run this in Terminal and paste the output. It shows which Safari version Carrier presents itself as on your Mac:
   grep -h "identifies as Safari\|native user agent" ~/Library/Logs/io.github.kristofferr.carrier/*.log | tail -2
2. Which Safari version do you have? (Safari → About Safari)

Thanks for the login screenshots too. That's being fixed separately.

[Anonymous]

Originally posted by: HomeStarRunnerTron

grep -h "identifies as Safari|native user agent" ~/Library/Logs/io.github.kristofferr.carrier/*.log | tail -2

This is what I get when I run that:

[2026-11-05][23:14:08][carrier_lib::user_agent][INFO] Messenger identifies as Safari 18.6 (WebKit 20621.3.11.11.3, system Safari 20621.3.11.11.3)
[2026-11-05][23:17:03][carrier_lib::user_agent][INFO] Messenger identifies as Safari 18.6 (WebKit 20621.3.11.11.3, system Safari 20621.3.11.11.3)

And when I look into my Safari (I use Brave Browser by default):

Version 18.6 (20621.3.11.11.3)

Rock rock on!

[Anonymous]

Originally posted by: kristofferR

[!NOTE]
🤖 Claude Opus 5.5 responding on behalf of Kristoffer, comment manually approved

Thanks, that helps a lot. Carrier is presenting itself as Safari 18.6 correctly, so it's past the browser check that 2.0.7 failed. The grey buttons come from a separate check Messenger only applies to end-to-end encrypted chats, and part of that check is decided on Facebook's servers.

One more test, if you don't mind: open facebook.com/messages in Safari itself, go to the same chat, and see whether the call buttons work there. If they're greyed out in Safari too, Facebook is blocking calls for Safari 18.6 (or for your account) rather than Carrier.

[Anonymous]

Originally posted by: HomeStarRunnerTron

Eyyy, whaddya know? They're completely greyed out in Safari, too. Are they not greyed out on newer versions of Safari?

[Anonymous]

Originally posted by: kristofferR

No, I tested that for the 2.1.0 release.

I'm working on a test to see if spoofing a newer Safari version number works though! 🙂

Thanks for the login page screenshots too, already fixed.

[Anonymous]

Originally posted by: kristofferR

[!NOTE]
🤖 Claude Opus 5.5 responding on behalf of Kristoffer, comment manually approved

Thanks for checking! Testing a newer Safari version number didn't help, unfortunately. Facebook doesn't decide this by version. In end-to-end encrypted chats, Messenger needs a WebRTC feature (createEncodedStreams) that Apple added to WebKit in Safari 26, and macOS 15's built-in WebKit (Safari 18.6) doesn't have it. Carrier uses the system's WebKit, so it matches Safari here: calls in encrypted chats work on macOS 26 and later, but not on macOS 15.

[Anonymous]

Originally posted by: kristofferR

BTW, I have a Macbook M1 myself, I recommend updating to macOS 27 TBH, works better than 15 did honestly.

[Anonymous]

Originally posted by: HomeStarRunnerTron

BTW, I have a Macbook M1 myself, I recommend updating to macOS 27 TBH, works better than 15 did honestly.

Good to know the reason, thanks for explanation and for your deep-dive into trying to figure this out. Thanks for letting me know -- I'm hesitant to update for lots of reasons, but I'll keep your vote in mind for later! : )

[Anonymous]

Ticket changed by: kristofferR

• status: open --> closed