Release 4.11.5 Client
  • 06 Jun 2022
  • 3 Minutes to read
  • Contributors
  • Dark
    Light
  • PDF

Release 4.11.5 Client

  • Dark
    Light
  • PDF

Article summary

Issues Resolved

HCXA-181 - PubLauncherSF doesn't display an error when it gets an unauthorized error condition

Observed

When publaunchersf gets an "unauthorized" from the Citrix Web API call to Resources/List, the application fails to launch, and publauncher just closes.

Resolution:

A popup message has been added that indicates "Unable to launch "AppName" for "UserName" because the authorization failed."

Affects Versions:

All prior versions

HCXA-39 - Memory leak in UserNotification.exe on Windows 10 when a large number of notifications are sent and the process runs for a long time

Observed

Sending a large number of messages to the user notification application on Windows 10 and Action Center connectivity is enabled (by default), UserNotification.exe memory growth is unbounded until it is restarted.

Resolution:

A bug in the action center component being used for notification didn't release event callback method references, so objects would not go out of scope. This has been resolved by a compiler update provided by the manufacturer.

Affects Versions:

All prior versions - only impacts Windows 10 installations

HCXA-194 - Loading a large number of apps for access control blocks running applications from querying XAUCM for the current user

Observed

While XA is loading the application list for a user login, the process is blocked from communicating with currently running applications. This in turn stops the Epic Proxcard Plug-in from retrieving the currently logged in user and completing the Hyperspace login on the Citrix server over the virtual channel communications layer. This makes it appear that the login is hung for up to 15 seconds (depending on how large the application list is, and how long it takes to retrieve the list from the server)

Resolution:

The login process has been modified to load the application list asynchronously so that queries for the user are not blocked.

Affects Versions:

All prior versions

HCXA-178 - Desktop links are not sorted case insensitive, and appear out of alphabetic order

Observed

Items are sorted based on the case of the characters "Xa d" appearing after "XA a" when the sort order if not case sensitive would be "XA A", "Xa d"

Resolution:

The comparison for sort now uses a case insensitive text check to determine where an item belongs in the display order.

Affects Versions:

4.11.0 and above

HCXA-197 - Catastrophic error message is displayed for the toolbar desktop when XA is configured for passthrough operation.

Observed

If the client is set for passthrough, and configured to display the toolbar desktop, the toolbar desktop application will display a "catastrophic error" message to the user with an OK button.

Resolution:

Because the expected application list is empty due to not being able to contact the server and retrieve a list of applications, parsing of an empty list failed. The empty list is now ignored and bypassed, allowing the process to complete without displaying an error.

Affects Versions:

All prior versions

HCXA-202 - RDP icon is missing from taskbar for rdpConnect when switching from full screen to windowed mode, and the window is minimized

Observed

When the Connector of XA client is set to use dual monitors and dual monitors are available, the taskbar icon disappears when minimizing the remote desktop application.

Resolution:

Adjustments to the window visibility have been corrected so that when switching from full screen to windowed mode, then minimizing the window, the application window displaying the icon is re-presented to the start bar, making the minimized application icon visible.

Affects Versions:

All prior versions

HCXA-188 - Prox card client service intermittently drops part of a card ID when checking for multiple readers and Indala RDR-6382 device(s) are attached

Observed

The ProxCard Client Service (hchidscan.exe) intermittently returns an invalid ProxCard id causing the user to get an incorrect user account if the ids match. Users would either be presented with an incorrect session (the invalid card was registered to another user already) - or they would be prompted to enroll the card as if it was newly issued.

Resolution:

Multi-card reader support calls APIs to activate a particular reader that appear to be interfering with properly reader a card ID from a device if there is only a single card reader attached to the PC. This API is no longer called unless there are multiple devices actually connected.

Affects Versions:

4.11.3 and above


Was this article helpful?