Release 2.29 (Aug 28)

In case you missed it, since our 2.28 release, we released Join by Browser for users on Google Chrome. We’re excited for this change to reduce issues related to the installation of our native app. The engineering team has followed this up with a burst of reliability improvements and bug fixes, while we also put the finishing touches on some upcoming features. With version 2.29, you’ll see new versions of the software for the Highfive device, the mobile apps, the desktop / browser app, and the web app.


  • Testing a general approach to improving screen share latency with a subset of call sessions. This does not apply to in-browser meetings.
  • Brought a new datacenter online for handling some customer meetings on the west coast of the United States.
  • Fixed a bug that would occasionally cause audio from phone callers to stop playing out to others in the meeting.

Highfive Device

  • Fixed an issue where Highfive devices connected to older TVs in 24Hz mode showed extreme screenshare lag and A/V sync issues. This was previously deployed as a hot-fix in 2.28.
  • On the Dolby Conference Phone, the volume control button clicking noise is now suppressed during meetings.
  • Improved the boot time of the Dolby Conference Phone.
  • Worked around a rare bug that causes the Highfive device to hang while waiting for a meeting. The workaround causes the Highfive device to restart when the hang occurs.

Desktop / Browser

  • Added full support for AirPods and other Beats/Apple W1 wireless headsets. This fix applies to the native app only; AirPods are already fully supported in the Chrome browser.
  • When selecting a Highfive device on Windows, Linux, and Chromebook computers, the in-browser app, or any device where Bluetooth is not enabled, the list is now automatically populated with most recently used devices.
  • Screen sharing now supports selection of individual Chrome tabs in addition to screens and windows.
  • Google OAuth and SAML authentication initiated from the native app now stays within the native app instead of opening the browser. This was required to allow native app users to keep using the native app even if their default browser is Chrome. We expect this behavior to be updated in a future release.


  • Fixed a bug preventing handoff to the app from Chrome on Android 8.0. This was previously deployed as a hot-fix in 2.28.

As always, Highfive does all the updating for you. Desktop apps and devices will automatically update over the next 24 hours, while updates to our mobile apps will be available in their respective app stores. Browser app changes and some desktop app changes are already available.

Still have questions?

We're here to help

Powered by Zendesk