8.56.29.54

New Features

Separate Application Logs
Added ability for applications to write their own logs, separate from runtime logs. When enabled, console messages including console.log, console.info, console.warn, and console.error are written to <rvmInstallDir>/<appHash>/app.log. To enable, set enableAppLogging=true in the startup_app property of your application config. RVM 4.0+ required.

Enhancements

• customData window option is now updatable
• Added Chromium reasons to the event payload for an unexpected close event
• Added closing as reason in hidden event when calling window.close
• Added Group Policy setting to set max socket connections per proxy server --max-connections-per-proxy=128
• Added support for 64 bit flash plugin.
• API Injection request is now done on a per window/frame
• Reduced payload when calling window.getGroup
• Added aeroGlassEnabled:true and screenSaver:false to System.getHostSpecs
• Additional Mac improvements

Resolved Issues

• Resolved a Deep Linking issue where parameters were not being passed on first launch
• Resolved a grouped windows issue where resizing one window would erroneously move other windows in the group
• Resolved issue associated with downloadAsset() callback behavior
• Resolved issues associated to the crash reporter not starting under certain conditions

Known Issues

• Failed configuring with PAC script, falling-back to manual proxy servers
  • Log Error: VERBOSE1:proxy_service.cc(1244)] Failed configuring with PAC script, falling-back to manual proxy servers.
  • This is a known Chromium bug fixed in Chromium 57. The application load should not be affected by this error however the client may notice a ‘Rouge’ opefin.exe process starting/stopping every X seconds. This bug could also leak memory, the standard work around is to add --winhttp-proxy-resolver as a runtime argument. We expect this issue to not persist with OpenFin v9+.