Skip to main content

Connect 4.1.3

Tera Insights Team
Tera Insights Team
tiCrypt Team

What is in this release​

CountSummary
New1Light theme
Change12On a system set to the light appearance, Connect now opens in the…; A version you install or pick by hand stays selected until you delete…; An update package that is not the version the update repository…; and 9 more
Fix20Update repositories are read again when the first address of their…; An update repository that cannot be read shows a message naming the…; Update repositories on a campus network or VPN (a server with a…; and 17 more

New​

  • Light theme. Connect follows your system's light or dark appearance

Changes​

  • On a system set to the light appearance, Connect now opens in the light theme instead of the dark blue one
  • A version you install or pick by hand stays selected until you delete it; an automatic update installs next to it without taking over
  • An update package that is not the version the update repository promised is refused with a message naming both versions, and is removed again
  • Each update is offered at most once per session; a failed update is offered again at the next start of Connect instead of after every click
  • Deployment URL fields fetch the deployment when you stop typing or press Enter, and every failed fetch shows the reason
  • Pushing to an SFTP drive keeps a file that already exists unless you choose to overwrite it, as on a local drive
  • SFTP drives refuse paths that climb above the folder the session started in
  • Folder pulls from cloud drives transfer four files at a time and finish several times faster
  • Google Drive: signing in shows Google's file picker, and the Google Drive drive lists only the files you pick there or picked at an earlier sign-in, including files on shared drives. Shared drives are no longer listed as separate drives, and folders cannot be picked. To add files, sign in to Google Drive again and pick them
  • tiCrypt starts and reloads faster: its files are unpacked once per launch and cached by the browser
  • macOS: the installer requires Apple silicon and refuses Intel Macs
  • Linux: Connect is installed from a package, an .rpm for Fedora or a .deb for Ubuntu 24.04, instead of a downloaded program file. The package installs the libraries Connect needs and adds tiCrypt Connect to the applications menu; a newer package upgrades it in place, and uninstalling removes it. Installing needs administrator rights (sudo). Your deployments, versions and settings are kept, and the program file you downloaded before can be deleted

Fixes​

  • Update repositories are read again when the first address of their server does not answer (for example IPv6 behind a VPN): installed versions update again and new deployments find their versions
  • An update repository that cannot be read shows a message naming the deployment and the reason instead of "No version installed"
  • Update repositories on a campus network or VPN (a server with a private address, such as 172.19.x.x) are read again, so Connect offers and installs their versions instead of refusing the address
  • Launching works when the tiCrypt server cannot be reached: Connect starts the application with the saved deployment configuration after at most 10 seconds
  • A failed launch clears the "Launching…" spinner and shows the server's reason, in the window and in a browser tab
  • A short network outage no longer shuts Connect down, unreachable deployments no longer flicker, and a failed deployment refresh shows a message
  • Database errors and damaged deployment records are reported instead of closing Connect
  • Simultaneous sign-ins no longer crash Connect, and a second launch while one is starting is refused at once
  • Closing the multi-factor sign-in window ends the sign-in instead of leaving it waiting; sign-in addresses and replies are no longer written to the log
  • A failed SFTP sign-in closes its connection to the server
  • OneDrive sign-in works again: Connect signs in without the client secret that expired (AADSTS7000222), so no secret ships in Connect and none can expire
  • Listing drives no longer fails once a drive is mounted, and signing out removes the account's drives
  • Mounted Dropbox, Box, Google Drive, OneDrive and SFTP drives stay mounted when the drive list is refreshed; opening one no longer fails with "specified drive does not exist"
  • Pushes to an SFTP drive land in the chosen folder on Windows, and a failed push stops cleanly
  • Pulls from cloud drives no longer upload a file twice when progress reporting fails
  • Windows: a failed drive refresh keeps the drives that were listed before
  • A VM connection whose tunnel dropped gets a new tunnel instead of crashing Connect
  • Version Manager: each date is shown only when it is known
  • Delete mode no longer hides the toolbar, so the changelog button and the Windows window buttons stay visible
  • macOS: Ctrl+C in a terminal or a shutdown signal quits Connect cleanly and saves the window position