
Can't download Mac PKG in 6.1.12232.6229
Hi,
Since updating to 6.1 I have been unable to download (or update) mac clients.
I upgraded to 6.1.12232.6229 to fix the black screen issue and still not ability to download the PKG. It doesn't even attempt to download. Have tried on multiple computers.
Answer

Good afternoon,
Have you defined an app.config file (this would be located in the App_ClientConfig directory in your base ScreenConnect installation directory)?
If so, please confirm the app.config file is properly formatted according to the template here: https://help.screenconnect.com/Creating_the_app.config_file#For_ScreenConnect_versions_5.3_and_above
In particular, please confirm that the configSections block looks like this:
<configSections> <section name="ScreenConnect.SystemSettings" type="System.Configuration.ClientSettingsSection" /> <section name="ScreenConnect.UserInterfaceSettings" type="System.Configuration.ClientSettingsSection" /> </configSections>
Also, does the Console/Network tabs in the browser dev tools provide any additional information when you click Download Installer (in Chrome, launch dev tools by typing F12)?
Cheers,
Ben

Hi Ben,
Here's my app.config file:
<configuration>
</configSections>
<ScreenConnect.UserInterfaceSettings>
<setting name="ShowBalloonOnConnect" serializeAs="String">
<value>false</value>
</setting>
<setting name="AccessShowUnderControlBanner" serializeAs="String">
<value>false</value>
</setting>
</ScreenConnect.UserInterfaceSettings>
</configuration>
Google Chrome reports:
GET http://support.XXX.ca/Bin/ClickRight.ScreenConnect.ClientSetup.pkg?h…XUzeV7hWEdl%2B4I6Ij8imujvV&e=Access&y=Guest&t=&c=test&c=&c=&c=&c=&c=&c=&c= 500 (Internal Server Error)
If you add the following line under <configSections> in your app.config, are you then able to build the OS X installer:
<section name="ScreenConnect.SystemSettings" type="System.Configuration.ClientSettingsSection" />
Regards,
Ben

I was experiencing the same problem: I could not upgrade or install 'access' clients for Macs. Adding this line to the app.config file did fix the problem. However, since this has never been a problem before, is this something that's going to have to be manually updated in the future?

This became an issue since we added app.config awareness to the Java client, upon which the OS X installer is based.
I registered an issue with development regarding the reported behavior, and a fix should be included in 6.1 stable.
Customer support service by UserEcho
This became an issue since we added app.config awareness to the Java client, upon which the OS X installer is based.
I registered an issue with development regarding the reported behavior, and a fix should be included in 6.1 stable.