---
title: "Workspot iOS Client Release 7.2.1"
slug: "workspot-ios-client-release-721"
updated: 2025-04-15T20:14:15Z
published: 2025-04-15T20:14:15Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.workspot.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspot iOS Client Release 7.2.1

## Highlights

- Released on April 12, 2025.
- Bug-fix release.

## Supported Operating Systems

iOS/iPadOS 17 and 18.

## **Installation**

Available in the [App Store](https://apps.apple.com/us/app/workspot/id617012477).

## **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.