Release Notes: IBM Aspera Connect 3.10.1
Product Release: October 20, 2020
Release Notes Updated: October 16, 2020
Release Notes Updated: October 16, 2020
Release 3.10.1 of IBM Aspera Connect is a maintenance release that provides the fixes and other changes listed below. These release notes also list system requirements, supported platforms, and known issues.
For information on the new features introduced with 3.10, see the release notes for Connect 3.10.0.
FIXED ISSUES
SYSTEM REQUIREMENTS
Note on browsers: The version numbers shown are for those browsers on which Connect was verified at the time of release; however, Connect is likely to work on later versions.
OS | Versions | Browsers |
---|---|---|
Windows |
|
|
Linux |
|
|
macOS |
|
|
- * Aspera plans to discontinue support for Microsoft Edge (Legacy) in a future release.
KNOWN ISSUES
- ASCN-2301 - Chrome does not detect Aspera Connect when the username contains an ampersand (&).
- ASCN-2274 - After upgrade, IE11 does not detect Connect until the browser is restarted.
- ASCN-2272 - [macOS] System proxy settings are not effective until the Connect app is restarted.
- ASCN-2232 - [Linux Gnome] Excessive system notifications appear saying "IBM Aspera Connect is ready".
- ASCN-2203 - [macOS] Connect 3.10 has no dark-mode support.
- ASCN-2069 - With file splitting, multi-session uploads are not distributed equally and incorrect transfer stats are reported.
- ASCN-2036 - Connect does not start automatically after a system-wide installation or upgrade. Workaround: launch Connect manually to fix the issue automatically.
- ASCN-1971 - Linux browsers installed using Snap cannot launch Connect.
- ASCN-1958 - A previously running transfer will be relaunched on application startup only if it is retryable
- ASCN-1852 - [Windows] Drag and drop fails when Chrome runs in high mandatory integrity mode. Workaround: Don't run as the built-in Administrator. (CIM-2690)
- ASCN-1851 - [Windows] Connect fails to open file dialogs when the browser's security integrity level is higher than Connect's. Workaround: Don't run as the built-in Administrator.
- ASCN-1829 - [Mac] Upgrade: progress bar stuck 'Verifying "Aspera Connect"...' Workaround: The stuck progress bar is related to Apple virus scanning and can usually be resolved by restarting the Connect application.
- ASCN-1698 - Connect crashes when user attempts to trust host too quickly.
- ASCN-1557 - After upgrading, drag-and-drop does not work until the browser is restarted.
- ASCN-1487 - [Mac] Safari extension-approval step appears even if the installation started in a different browser.
- ASCN-1295 - When encrypted files are downloaded, there is no "Protected Content" dialog asking for a passphrase to unlock the files being transferred or to keep the files encrypted. The files are still downloaded, so the files can be decrypted later after download.†
- ASCN-797 - Main menu bar for Crypt is not translated for all languages.
- ASCN-754 - [Windows] Internet Explorer crashes during a Connect upgrade.
- ASCN-705 - If Connect is not able to connect to the server through SSH, a misleading error message, "Failed to authenticate," is reported rather than indicating it's a connection problem. (CIM-72)
- ASCN-580 - [Windows] Accessibility: Install wizard not properly displayed in high contrast mode.
- ASCN-271 - When encrypted-at-rest files are downloaded, the decryption dialog does not ask for passphrase confirmation. As a result, if the passphrase is invalid, the files are transferred in their encrypted state. (CIM-635)
- ASCN-262 - JAWS does not say how to select hosts from the hosts list in the Security sub-tabs. This issue is found in other Security sub-tabs, as well.
- ASCN-149 - Connect does not switch "desktops" to reveal Connect when asking the user to select files or folders. Workaround: Select Connect from the dock.
PRODUCT SUPPORT
For online support, go to the IBM Aspera Support site at https://www.ibm.com/mysupport/. To open a support case, log in with your IBMid or set up a new IBMid account.