Using CWA Mac 2508 it is necessary to click twice to move focus to another application inside a published desktop. 

The issue is reproduced as follows. 

1. Start the ICA session in desktop mode.
2. Switch desktop viewer to window mode
3. Open any local app on Mac and put input focus into the app window
4. Click any windows on VDA 

 
You need to click two times to activate the window, or to click the button, or to set the input focus 

Citrix is not responsible for and does not endorse or accept any responsibility for the contents or your use of these third party Web sites. Citrix is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement by Citrix of the linked Web site. It is your responsibility to take precautions to ensure that whatever Web site you use is free of viruses or other harmful items. 

This is also reproducible outside of Citrix in Mac OS . 

For instance, using Finder with Slack, or Finder with PowerPoint, 

When focus is on Finder, and you want to click any button or content in Slack or PowerPoint you need to click 2 times. 

The first click just activates the app, and then the second click can control the app. 

Citrix Desktop Viewer from CWA mac 2508 was built by xcode 16  

Issue may not be observed on earlier versions such as CWA Mac 2409 since this was not developed using xcode 16 

Please contact Apple for further information. This is a Mac OS issue .

However Citrix is also working on a possible  enhancement to the CWA Mac to resolve this issue . Reference HDX-91545.

Using CWA Mac 2508  it is necessary to click twice to move focus to another window inside a published desktop.

See https://developer.apple.com/documentation/appkit/passing-control-from-one-app-to-another-with-cooperative-activation 

MacOS now uses "cooperative activation". Apps request activation from the system, and the system decides whether to grant it. 

As a result, clicking on an inactive window often only activates the app on the first click; a second click is typically required to interact with window content. This is a system-level behavior, not an application bug.