Skip to main content
Known Participant
January 15, 2013
Question

Chrome is and isn't supported?

  • January 15, 2013
  • 1 reply
  • 966 views

Just tried launching my first v9 share session with the Host on IE9 and the Participant on Chrome 23.0.1271.97 m.


As soon as the Chrome user accepted my screen share request they got this adorable error:

"Adobe Connect Add-in is incompatible with default settings of your version of Google Chrome.

While we work on a solution, please change your default settings as explained here or use another supported browser."

The link in the message goes to a non-existant article: "Sorry, this page is not available"

I used the Google cache of the page (here) and, when clicking on the links displaying "supported browsers", I get another page that indicates Chrome is a supported browser:

Client system requirements: Hosted and licensed deployments

The following tech specs are for Adobe Connect 9.

Adobe Connect 8.x tech specs can be found here.

Windows

  • 1.4GHz Intel® Pentium® 4 or faster processor (or equivalent) for Microsoft® Windows® XP, Windows 7 or Windows 8; 2GHz Pentium 4 or faster processor (or equivalent) for Windows Vista®
  • Windows XP, Windows Vista, Windows 7, Windows 8
  • 512MB of RAM (1GB recommended) for Windows XP, Windows 7 or Windows 8; 1GB of RAM (2GB recommended) for Windows Vista
  • Microsoft Internet Explorer 7, 8, 9, 10; Mozilla Firefox; Google Chrome
  • Adobe® Flash® Player 10.3

 

Mac OS

  • 1.83GHz Intel Core™ Duo or faster processor
  • 512MB of RAM (1GB recommended)
  • Mac OS X, 10.5, 10.6, 10.7.4, 10.8
  • No Adobe Connect Add-in support for Mac OS X 10.5 (Leopard). Users on Leopard can attend meetings in the browser.*
  • Mozilla Firefox; Apple Safari; Google Chrome
  • Adobe Flash Player 10.3
This topic has been closed for replies.

1 reply

Jorma_at_Knox
Legend
January 16, 2013

Here is the current page for that... http://helpx.adobe.com/adobe-connect/kb/google-chrome-browser-incompatibility.html

Someone must have fast fingered that link as it has version a the end of it, and it shouldn't.

The problem comes down to Chrome using a new API for flash functionality, if you change the API in the settings for Chrome it can work. However, the easiest solution is to use a different browser.