Citrix Receiver for Android 3.7.3 is the current version on Google play. Users running prior versions should update to the latest version.
Citrix Receiver for Android 3.7.3 includes support for Android M (6.0).
Issues fixed in 3.7.3
Citrix Receiver for Android 3.7.3 addresses intermittent crashing when Citrix Receiver is used with Nexus 9 Bluetooth.
This recent update includes:
- Fit to display. When publishing an app with a specific resolution, Receiver now displays the app in a central area and scales the display depending on the aspect ratio; it properly interprets the relationship between the source (app) and the destination (the display).
- Enhanced support for mirroring the session display. Receiver for Android enhances the user experience by matching the display characteristics between the screen display and the Android device.
- Support for Transport Layer Security (TLS). Receiver for Android now supports TLS 1.1 and TLS 1.2 protocols. When enabled, TLS provides secure communication between the server and client. This functionality can be configured using the interface or through the receiverconfig file.
- Support the hiding of in-session menu bar for devices without touchscreen support.
- Improved keyboard handling of the Korean Hangul alphabet.
The following issues and limitations are known at this release of Receiver for Android:
- In the previous release, limited support was provided for mirroring the session display to a second display; a limitation existed where only devices whose resolution matched the display of the Android device were supported. At this release of Receiver for Android, this limitation has been removed - display devices whose resolution differ from the Android device are supported, with the following limitations: [#549471]
- Session size is determined by the natural resolution of the attached display device; all other settings are ignored because the second display cannot scale the session image. In addition, requests to dynamically adjust the session resolution to match the resolution of an attached display are only partially supported. In such environments, connecting and disconnecting a second display will not allow you to request a resize of the session that observes the normal user settings.
- Instability may occur when disconnecting a second display, causing Receiver to crash. It is suggested that when using a second display you connect it to your Android device before starting your session.
- Display performance may be negatively impacted in the attached display; in some cases, the attached display may occasionally experience cosmetic faults, such as faulty display of the mouse pointer and tearing during window moves.
- Some limitations apply to the user interface as displayed on the primary display of the Android device. For example, the mouse operates to a device's screen dimension, and not to secondary screens. Additionally, no toolbar is displayed on the device screen when screen mirroring is enabled. [#549471]
- When attaching a secondary display, the screen resolution of the newly attached display is the same resolution as the device. This issue occurs when the connected device is docked after the session is initiated, and when the mouse is not attached to the dock. To resolve this situation, attach the mouse for the second session to return to the correct resolution. This issue applied specifically to the Samsung Galaxy Note II Multimedia Dock. [#541028]
- Removing the mouse from a docked session causes the screen display on the device to rotate 90 degrees clockwise. Session orientation returns to normal after a short period of time. This issue applied specifically to the Samsung Galaxy Note II Multimedia Dock. [#541032]
- When using screen mirroring to an external monitor using an AllCast dongle, no audio is heard when playing media files. This issue appears to be related to the capability of the display device; if a TV with speakers is used, audio output occurs through the TV. If a monitor with no speakers is used, the expectation is that speakers on the Android device would be used, however, this is not the case.[#544330]
- Moving the magnifier to the outer most edge of the session image may cause the magnifier to display part of the unmagnified background image. [#542299]
- On some occasions, closing a session may result in a run time exception. [#523824]
- Maximum 'Pinch Out' level is not maintained after screen rotation. This event may occur after launching a session and using 'Pinch In' to attain the maximum desired view, and then rotating the device 90 degrees; after rotating the device a second time, the previously selected 'Pinch Level' is not maintained. [#538638]
- The extended keyboard is erroneously activated in certain conditions; in some cases, this occurs when screen mirroring is stopped and the device is rotated, in other cases this may occur when the device screen is touched while screen mirroring is enabled. These issues may occur when the Android device is unable to determine whether the soft keyboard is showing; entering mirror mode by connecting another monitor fails to interpret the act of displaying the extended keyboard. [#545231]
- Account creation fails for ASUS Nexus 7 devices running Android version 4.1.1. To prevent this issue, update the device to the latest Android software, such as 4.2.2.
- On some Android devices, the Bluetooth Mouse right-mouse click continues to invoke the Back action, causing the Exit dialog box to appear unintentionally. This issue occurs only on devices with firmware that does not support the right-mouse click. [#331168]
- In Receiver for Android 3.5, the Full VPN Tunnel feature is not supported when you use smartcard authentication. [#456657]
- When you connect to an FIPS NetScaler while the "denysslreneg" policy is set to No or Frontend Client and "Client Authentication" is set to Optional, you may encounter the following error when you log in to Receiver.
- When you log in to Receiver by entering "Domain\username" in the username field, you may receive a prompt that your username or password was incorrect . This prompt displays Domain\Domain\username in the username field. To resolve this issue, remove one of the domain name entries and log in again using the domain|username format. [#466022]