Workspot iOS Client Release 7.0.0
by Robert Plamondon
Last updated April 8, 2024
Highlights
- Available in the App Store.
- Support for the Company Identifier tag, which supports multiple Control instances for data sovereignty.
System Requirements
iOS 16 and 17.
Known Issues
- An external mouse will sometimes leave a faint trail on the display.
- With Web Applications, the Client ignores any URLs the administrator has added to Control's URL blacklist, allowing access to these sites.
- When using an external Magic Keyboard, left-clicking the trackpad mouse can crash the Client when using a Web application. This does not occur with Workspot desktops or RD Pool applications.
- 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 that were 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 "publshed 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.