How to convince Safari to open the new BlueJeans app on MacOS?

  • 1
  • Problem
  • Updated 6 months ago
  • (Edited)
It seems that whatever I do and even if I follow the BlueJeans removal document from ... when I click a BJ link in Safari or even on any other application on the operating system (Safari is default browser), it will always start the old "Blue" instead of "".

After removing the old app Safari no longer prompts me to open BJ app, I only get the windows that ask me to Allow it to open...

I mention that I even manually whitelisted domains from popup permissions, hopping that this may make it work, but it doesn't.

I mention that the behavior is different Safari 11 and on Safari 12 (beta):
* Safari 11 : clicking the url opens a window that downloads the DMG Launcher,... which mainly installs the OLD BJ app.
* Safari 12 : same url, opens the window above which was supposed to prompt to start the application, but no prompt happens.

Clearly BJ fails to use the URL handler approach for starting the native application which is the only portable way of starting an application which would be working with any operating system Windows, Linux, MacOS, Android, iOS and any browser. Use of custom plugins seems to be a permanent source of problems.

Does anyone know a temporary workaround to make this work? Being forced to copy url, paste it in another text editor, extracting the meeting id, copying it and pasting it into the BJ app is a huge PITA. The pain is even worse when people are sharing custom urls, as the new BJ app fails to use nicknames instead of meeting numbers, so you also have to find a way to translate the nice url to a meeting id.

Before some smart guy from support mentions that "use of unreleased software is not supported by BlueJeans", keep in mind that both MacOS Mojave and Safari 12 are going to be released in less than a month from now and testing versions were available for many months before that. I am ready to bet that BlueJeans will be again broken, when this will happen... and this should not come as a surprise. 
Photo of ssbarnea


  • 122 Points 100 badge 2x thumb

Posted 6 months ago

  • 1
Photo of Don L - BlueJeans

Don L - BlueJeans

  • 60 Points
I did verify that your company has the v2.x.x update off at an enterprise level. This means that the join flow will not push you to the new v2.x.x and you would have to use v1.x.x app for the moment until your company decides it is time to move to the new app v2.x.x.

Although, this can be enabled on a per user basis.