Workspot iOS Client Release 7.2.0

Highlights

  • The Beta release is available now.

  • Production is scheduled for November 30, 2024.

  • Support for iOS 18.

  • The Client now reports when a user's attempt to reboot a Workspot desktop has failed.

Supported Operating Systems

iOS/iPadOS 17 and 18.

Beta Installation via Apple TestFlight

Beta releases are handled through Apples TestFlight program. We provide a link for each Beta release. Clicking this link on your iOS device takes you to a Web page that invites you to install Apple’s TestFlight app if you haven’t already and to join the Beta program for the individual Beta release.

Use this TestFlight link: Workspot iOS Client 7.2.0 Beta.

Installation

Will be available in the App Store upon release.

Known Limitations

  • In iOS 16, the on-screen keyboard may obscure parts of the Workspot desktop sign-in fields on the first launch of a non-persistent desktop.

  • When a power-managed desktop resumes from sleep, the connection may time out prematurely with the error "There was a problem starting your desktop. Please contact your administrator." The end-user should retry the connection BEFORE contacting the administrator, since this usually works.

  • In the Procura app, dragging a subwindow leaves a trail of duplicate subwindows.

  • If you launch and then cancel the same desktop or app twice before it connects, it will not connect when you launch it for the third time.

  • Web Apps not designed for or tested with iPhones may require extra scrolling.

  • When updating to a newer version of the Workspot Client, two Client icons are shown on your device. The duplicate icon is deleted once the new version is fully installed.

  • On published apps, the "published app" icon may overlap the "Minimize" button.

  • Some Web Apps may not display or function properly if the Web server expects only certain browsers/device combinations.

  • On the UK-layout Magic Keyboard, Control, Option, and Command key sequences do not work.

  • When multi-factor authentication is used, no error message is given if the multi-factor challenge is ignored by the user.

  • When a user launches a desktop and cancels it before it opens, the next launch will not complete. Workaround: cancel the second launch. The next launch will work normally.