Release Notes: IBM Aspera Connect 4.0.0
Release Notes Updated: April 29, 2021
Release 4.0 of IBM Aspera Connect provides the new features, fixes, and other changes listed below.
The remaining content of these release notes describes the new features, fixes, and other changes introduced with Connect 4.0, and also includes system requirements, supported platforms, and known issues.
NEW FEATURES
IBM Aspera Drive features have been integrated into Connect. Customers looking to use the latest Drive features must upgrade to Connect. (Aspera/connect-app#210)
Beta support for Faspex 5. (Aspera/connect-app#168)
Connect supports dark mode for macOS. (Aspera/connect-app#592 ASCN-2203)
Designate a file as the signature file (on either the local or remote storage, or both). Before starting the sync, Connect verifies that the signature file exists. If the signature file cannot be found, Connect halts the sync to prevent accidental deletion. (Aspera/connect-app#192)
BREAKING CHANGES
Connect no longer supports Internet Explorer 11 and Microsoft Edge (Legacy). (Aspera/connect-app#533 ASCN-754 ASCN-1557 ASCN-2274)
If you do not uninstall Drive after upgrade, you may see a duplicate "Aspera Drive" icon in your Windows Explorer, based on whether Drive was installed system-wide and whether Connect is installed system-wide. Workaround: In all cases, uninstalling IBM Aspera Drive fixes all issues. (Aspera/connect-app#617)
Connect must be installed on 64-bit Windows. (Aspera/connect-app#133)
The Connect SDK will no longer include v2 code (asperaweb-2.min.js and connectinstaller-2.min.js, for example). (Aspera/connect-sdk#21)
FIXED ISSUES
Aspera/connect-app#490 - Connect cannot parse transfer specification paths if a path entry has any key other than "source" and "destination".
Aspera/connect-app#188 - Sync session fails to shutdown after repeated disconnects. (ASDR-2876)
Aspera/connect-app#180 - Error messages in the error pop up window can be copied using both keyboard shortcuts and mouse right-click context menu. (ASDR-2154)
Aspera/connect-app#186 - Sync fails if AoC workspace name contains a forward-slash. (ASDR-2869)
Aspera/connect-app#99 - AoC workspaces that cannot be synced can still be selected for sync.
Aspera/connect-app#73 - Users cannot download packages from Aspera on Cloud shared inboxes inherited from group membership.
Aspera/connect-app#38 - On file systems that don't support change notifications, continuous sync mode scans only once instead of on an interval.
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 |
|
|
| macOS |
|
|
Server Requirements
One of the following:- IBM Aspera Shares - a currently supported version
- IBM Aspera Faspex - a currently supported version
- IBM Aspera High-Speed Transfer Server (HSTS) - 3.9.6 or higher recommended
To use Connect's Aspera Drive synchronization features, the server must have a Sync-enabled license.
KNOWN ISSUES
ASCN-2332 - [macOS] Selecting "Open containing folder" occasionally does not open a Finder window.
ASCN-2301 - Chrome does not detect Aspera Connect when the username contains an ampersand (&).
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-2069 - With file splitting, multi-session uploads are not distributed equally and incorrect transfer stats are reported. Workaround: Disable file splitting. (ASDR-2799)
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 retry-able.
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-1841 - Connect prompts can be hidden behind other windows when switching applications.
ASCN-1829 - [macOS] 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-1815 - For downloads, the EAR passphrase dialog can become hidden and hard to find.
ASCN-1698 - Connect crashes when user attempts to trust host too quickly.
ASCN-1487 - [macOS] 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-705 - If Connect is unable to connect to the server through SSH, Connect issues a misleading "Failed to authenticate" message rather than indicating it's a connection problem. (CIM-72)
ASCN-580 - [Windows] Accessibility: Install wizard not properly displayed in high contrast mode.
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.
ASDR-2748 - Multi-session is not compatible with HTTP fallback. Use one or the other.
ASDR-2319 - macOS security may (mistakenly) indicate that Drive is attempting to access your Contacts or Calendar. Drive does not access your Contacts or Calendar for any purpose.
ASDR-2173 - [Mac] When a user tries to send a file by selecting Share > Aspera Drive, the send-to window doesn’t open, and the Sharing with Aspera Drive... pop up remains open on the screen.
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.