3CX Chrome Extension on MacOS

[daveGradwell]

MacOS users appear to have lost the functionality of a 'floating' Chrome Extension
between browser tabs. Indeed, in the forum post, we see

https://www.3cx.com/community/threads/macos-customers-forgotten-or-abandoned.83375/

The 3CX Browser extension used to offer the following:
- Appeared as a separate dialer detached from the web browser.

Can you either reinstate a Chrome client Extension with usable hot keys,
or release a MacOS app like you have for Windows? Are there any workarounds you could
suggest and is there continuing development with the Extension to restore features?

 

[Weble Srl]

I have to agree with Dave here.

Up until v17, a mac user could either use the old v16 Mac app or the chrome extension.
Since you've discontinued the Mac Desktop app, and now with v18 you've removed the possibility to use the chrome extension as the client, what are we supposed to tell our mac users?

The only solution is to keep the old mac app (which you said it will eventually break) or keep a web tab open to the web client, which hardly seems a good user experience.

Any hints?
Thanks
Daniele

 

[paulsummers]

This has caused us significant issues this morning. What is the recommended advice for MacOS users?

 

[Lisa Hammerton]

If you are on v16 and can move to v18, then do so asap and you can re-install the old extension for your Mac or Linux users. Windows users will receive the brand new windows desktop app which is much better than the old extension. Of course, they can continue using the old Windows app if they prefer. Mac users will receive a new mac client shortly.

This comment from the CTO and founder suggests the old app will work. But no suggestion of the date when the new client will be released.

 

[RTPch]

This is a major problem! All our employees used the Chrome Extension as a softphone which apparently no longer works. But without macOS Client this is useless...

When will we get the updated maOS client?

 

[Lisa Hammerton]

This is a major problem! All our employees used the Chrome Extension as a softphone which apparently no longer works. But without macOS Client this is useless...

When will we get the updated maOS client?

3CX have stated.

After an internal discussion we have decided following:|

A. We are going to fast track a Mac OS desktop app and try to get an alpha version as soon as possible, i.e. within the next week.
B. We are going to release a beta of v16 that has the ability to work with the old extension. It will still require re install of the old extension. We will try to do this in the coming days.

We're currently testing on MAC to see if the old app works.

 

[Lisa Hammerton]

This is a major problem! All our employees used the Chrome Extension as a softphone which apparently no longer works. But without macOS Client this is useless...

When will we get the updated maOS client?

We've tested this with a MAC and the old chrome extension works. Here is the link: https://chrome.google.com/webstore/detail/3cx/dijllljhgnommpcoogbfcnadmnleeook

 

[paulsummers]

Sorry don't understand, what is the v16/v18 debate? Is the suggestion here to downgrade to 16? This all seems rather poorly planned and certainly not well communicated.

 

[paulsummers]

We've tested this with a MAC and the old chrome extension works. Here is the link: https://chrome.google.com/webstore/detail/3cx/dijllljhgnommpcoogbfcnadmnleeook

Chrome extensions, if I'm understanding this correctly, they've made a direct switch of the chrome extension and changed the functionality wholesale then quickly made the old version available as a new extension in the chrome store?

 

[RSIT]

This is really a big issue for Mac users, just had a whole office miss various calls due to this questionable practice. At least they could have waited with switching the extension until the V18 Mac desktop app finally gets released. On that front I also only keep hearing "it's in the pipeline", at least a tentative release timeframe would make it easier to communicate this to clients.

 

[NickD_3CX]

If you have V18, what you need to do for your MacOS users is:

1. Upgrade the server to V18 U2
2. Follow the steps outlined here: https://www.3cx.com/community/threa...s-contacts-and-team-members.86335/post-407386

This will make the "floating" dialer become available again.

[EDIT]
To add to what I wrote above, do that if you are on V18 U1.

If you are on V16 U8a, we released a small update for V16 users that can bring back the "floating" dialer temporarily.
Information about this can be found here: https://www.3cx.com/blog/releases/v16-update8a-beta/

Important!
Read the "Recommended options" section well to understand why I am calling this a "temporary solution".

 

[roadmapit]

I have to say as a customer with Mac users this seems like a complete mess. Certainly poorly communicated and has left a lot of our customers rather angry. Ourselves included.

It did not need to be done this way which is the most disappointing. Why not hold until you have feature parity rather than what you have pushed clients through.

 

[MarcGold]

If you have V18, what you need to do for your MacOS users is:

1. Upgrade the server to V18 U2
2. Follow the steps outlined here: https://www.3cx.com/community/threa...s-contacts-and-team-members.86335/post-407386

This will make the "floating" dialer become available again.

[EDIT]
To add to what I wrote above, do that if you are on V18 U1.

If you are on V16 U8a, we released a small update for V16 users that can bring back the "floating" dialer temporarily.
Information about this can be found here: https://www.3cx.com/blog/releases/v16-update8a-beta/

Important!
Read the "Recommended options" section well to understand why I am calling this a "temporary solution".

Hi Nick,

Thanks for the update, what a fiasco. However the instructions don't works as expected when using MS Edge on the MAC (which is chromium). Server is already V18 U2, and the extension installs. But when you goto setting, personalise (to change the audio device to the headset) then whole browser panics and crashes.

 

[NickD_3CX]

Hi Nick,

Thanks for the update, what a fiasco. However the instructions don't works as expected when using MS Edge on the MAC (which is chromium). Server is already V18 U2, and the extension installs. But when you goto setting, personalise (to change the audio device to the headset) then whole browser panics and crashes.

I think this may actually be a "Edge for MacOS" bug, rather than an issue with the update or extension. Regardless what happens, the browser should not crash (Edge for MacOS running on the new M1 chip has not had the smoothest ride so far....).

Anyway, could you try if the same happens if you use Chrome?

 

[MarcGold]

I think this may actually be a "Edge for MacOS" bug, rather than an issue with the update or extension. Regardless what happens, the browser should not crash (Edge for MacOS running on the new M1 chip has not had the smoothest ride so far....).

Anyway, could you try if the same happens if you use Chrome?

Hi Nick
I had exactly the same thought after sending you the message.

Yes it does work on Chrome.

Interestingly, the webclient also crashes MS Edge when trying to adjust the audio settings. Or make or receive a call.

All the Mac's are 2019 Intel's, we haven't been brace enough to introduce the M1 as you say, lots of compatibility issues still.
Regards.
Marc

 

[NickD_3CX]

Hi Nick
I had exactly the same thought after sending you the message.

Yes it does work on Chrome.

Interestingly, the webclient also crashes MS Edge when trying to adjust the audio settings. Or make or receive a call.

All the Mac's are 2019 Intel's, we haven't been brace enough to introduce the M1 as you say, lots of compatibility issues still.
Regards.
Marc

Thanks for checking this Marc, although there are a lot of users that are using Edge on MacOS without issues, I'm not sure why yours is crashing.

Regardless though, I think the solution for you is to use Chrome, for the time being at least.