History of Secure Hub known and fixed issues

Last published : Oct 12, 2026
This article lists fixed and known issues for Secure Hub for versions earlier than the recent supported versions. For the most recent documentation, see Citrix Secure Hub.

Secure Hub for Android 23.7.0

Fixed issues

  • On the Android Enterprise platform, the Managed Configurations policy might not apply to the device after enrollment.
  • On the Android Enterprise platform, the required Public App Store app might not install automatically on the device after enrollment.
  • When you reboot your device and don’t unlock it, you might not be able to reset the device passcode through the lock command that is issued by the IT administrator.
    This method is helpful in case the end user loses their device passcode or loses the device, they can ask the administrator to reset the device passcode or lock the device through the lock command.
  • When end users open Secure Hub on certain Android devices for enrollment, the Secure Hub app becomes unresponsive
    The issue occurs when MDM enrollment fails due to an expired license. Consequently, the Secure Mail app is unavailable.
  • When you configure Citrix Gateway as the identity provider (IdP) for authentication purposes, and the network connection to the gateway is unstable, authentication fails, and end users can’t sign in to Secure Hub.

Known issues

There are no known issues in this release.

Secure Hub for iOS 23.4.0

Fixed issues

This release addresses a few issues that help to improve overall performance and stability.

Known issues

There are no known issues in this release.

Secure Hub for Android 23.4.1

Fixed issues

  • A loading spinner UI appears when you start the Secure Hub app. This issue occurs due to a deadlock condition.

Known issues

There are no known issues in this release.

Secure Hub for Android 23.4.0

Fixed issues

  • After you upgrade a device from Android 11 to Android 12 and then to Android 13, the Secure Hub app fails to start.
  • After you enroll in a corporate owned single use (COSU) device, the Secure Hub app requests an active directory (AD) password instead of Citrix PIN. The issue might occur due to loss of cached credentials in Secure Hub version 23.2.0 and earlier.
  • Secure Hub app becomes unresponsive as the PIN is not accepted due to an exception in the code.

Known issues

There are no known issues in this release.

Secure Hub for Android 23.2.0

Fixed issues

  • After you enroll in a corporate owned single use (COSU) device, and the restrictions policy allows the use of SD cards, you still might not be able to access the external SD card on these devices. The issue is that it is a dedicated device.
  • The passcode policy settings for password expiration on Android Enterprise devices do not work as expected. The passcode change prompt doesn't appear. Instead, you have to change the passcode manually.
  • Occasionally, after you upgrade a device from Android 11 to Android 13, the Secure Hub app becomes unresponsive.
  • Each time you sign in to Secure Hub, the app requests active directory (AD) password instead of Citrix PIN. The issue occurs after you have changed the AD password.
  • After you change the active directory (AD) password, attempts to sign in to Secure Hub fail with the following error message:
    Incorrect credentials.

Secure Hub 22.11.0

  • When a push message is sent from the CEM console to the Enrollment App channel, the message arrives on the device but does not trigger the sound alert.
  • When you configure the Credentials Policy and define the certificate alias, the Citrix SSO app fails to connect to the VPN with an authentication error when using the custom certificate alias. The following error message appears:
    Connection Error: Cannot connect to the certificate ID. Check your internet connection and verify the settings for certificate ID.
    The issue occurs when you allow apps to use the certificates for the Citrix SSO app.

Secure Hub 22.9.0

There are no known or fixed issues in this release.

Secure hub 22.7.0

Fixed issues

  • After you switch from Mobile Device Experience (MDX) to Citrix Mobile Application Management (MAM) SDK, and upgrade XenMobile Server to 10.13 RP4, you might not be able to access intranet sites through Secure Hub/ Secure Web.
    The following error message appears: "Err_Name_not_resolved".
  • The managed configuration policy settings are not applied on work profiles that have the enrollment configuration as Work Profile for Company Owned Devices (WPCOD). The issue occurs when the authentication is through the Identity Provider (IdP), and the Work Profile isn't marked as provisioned.

Secure Hub 22.6.0

There are no known or fixed issues in this release.

Secure Hub 22.5.0

There are no known or fixed issues in this release.

Secure Hub 22.4.0

There are no known or fixed issues in this release.

Secure Hub 22.2.0

Known issues in Secure Hub 22.2.0

There are no known issues in this release.

Fixed issues in Secure Hub 22.2.0

Secure Hub for iOS

  • In Secure Hub for iOS, you are prompted to enroll using a PIN on devices enrolled through the Apple Deployment Program.
  • When you sign in to Secure Mail after your device has been idle, Secure Hub for iOS opens with the following error message:
"Secure Hub needs to authorize this app."
Once you click authorize and provide your credentials, authentication goes into a loop. You can't reauthenticate or sign in even after a reboot.
  • Secure Hub for iOS becomes unresponsive on devices running iOS 15.1 when you are reporting an error.
  • In Secure Hub for iOS, the badge count appears as 1 or 2 despite there being no new notifications.
  • In Secure Hub for iOS, enrollment might fail on some devices.
  • If you configure the Citrix Gateway Session time-out policy value to 30 days, Secure Hub for iOS prompts users to reauthenticate every 24–72 hours.

Secure Hub for Android

  • In the Samsung DeX mode, Secure Hub becomes unresponsive when you enter the PIN.
  • When you enroll Samsung S20 devices, in the fully managed mode, to Android Enterprise, the following error appears: "Invalid server certificate"
  • Enrollment of devices running Android 10 or 11 fails and the following error message appears: "Security policy does not allow you to connect".
  • When you enroll to Secure Hub for Android, your credentials are replaced with random numbers if you switch from portrait to landscape mode.

Secure Hub 21.11.0

Known issues in Secure Hub 21.11.0

There are no known issues in this release.

Fixed issues in Secure Hub 21.11.0

Secure Hub for Android

  • During enrollment in Secure Hub for Android, the No certificates found error message appears. When you click Install certificate, an empty link, without any certificate, appears. If you click Cancel, the authentication screen appears. This issue also occurs when you sign out and sign in to Secure Hub.

Secure Hub 21.10.0

Known issues in Secure Hub 21.10.0

There are no known issues in this release.

Fixed issues in Secure Hub 21.10.0

Secure Hub for iOS

  • In Secure Hub for iOS, you are prompted to enroll using a PIN on devices enrolled through the Apple Deployment Program.

Secure Hub for Android

  • When creating an enrollment profile for Android devices to enroll in work profile on corporate-owned devices mode, you must enable the BYOD work profile setting. If you don't enable this setting, devices fail to enroll.
  • While signing in to Secure Hub for Android, the email ID is auto populated.

Secure Hub 21.8.0

Secure Hub for iOS

Known issues in Secure Hub 21.8.0

There are no known issues in this release.

Fixed issues in Secure Hub 21.8.0

  • When you log in to Secure Mail after your device has been idle, Secure Hub for iOS opens and attempts to log on but the logon request fails. Secure Mail continues to prompt for logon and creates a sign-on loop.
  • Users with certain special characters in their user name or password can't enroll.

Secure Hub 21.7.1

Secure Hub for Android

There are no known or fixed issues in this release.

Known and fixed issues in earlier versions

For known and fixed issues in earlier versions of Secure Hub, see History of Secure Hub known and fixed issues.

Secure Hub 21.7.1

Secure Hub for Android

There are no known or fixed issues in this release.

Secure Hub 21.7.0

Secure Hub for iOS

There are no known or fixed issues in this release.

Secure Hub for Android

Known issues in Secure Hub 21.7.0

There are no known issues in this release.

Fixed issues in Secure Hub 21.7.0

  • In Secure Hub for Android, Secure Mail and Secure Web logs are missing when you navigate to Help > Report Issue after you reboot your device.

Secure Hub 21.6.0

Secure Hub for iOS

Known issues in Secure Hub 21.6.0

There are no known issues in this release.

Fixed issues in Secure Hub 21.6.0

In Secure Hub for iOS, when you enroll a device using User Principal Name (UPN), the user name does not auto-populate. This issue occurs when Auto Discovery Service is enabled.

Secure Hub for Android

Known issues in Secure Hub 21.6.0

In Secure Hub for Android, you cannot enroll a device in the MDM+MAM mode if the FQDN provided contains capital letters. Instead, the device in enrolled in MAM mode.

Fixed issues in Secure Hub 21.6.0

In Secure Hub for Android, you are unable to enroll factory reset devices running Samsung Knox in the Device Administrator mode.

Secure Hub 21.5.1

Secure Hub for iOS

There are no known or fixed issues in this release.

Secure Hub for Android

There are no known or fixed issues in this release.

Secure Hub 21.5.0

Known issues in Secure Hub 21.5.0

There are no known issues in this release.

Fixed issue in Secure Hub 21.5.0

In Secure Hub for Android, you are unable to deploy the Wi-Fi device policy on Android Enterprise devices. The policy remains in the Pending state.

Secure Hub 21.4.0

There are no known or fixed issues in this release.

Secure Hub 21.3.2

Secure Hub for iOS

Known issues in Secure Hub 21.3.2

There are no known issues in this release.

Fixed issue in Secure Hub 21.3.2

You are unable to enroll a device on Citrix Endpoint Management™, after entering the Citrix PIN. Secure Hub does not display the correct message for the PIN requirement.

Secure Hub 21.3.0

Known issue in Secure Hub 21.3.0

In Secure Hub for Android version 20.9.0 and later, you can’t connect in VPN mode on Google Pixel 2 devices.

Fixed issues in Secure Hub 21.3.0

  • In Secure Hub for Android, the Integrated Circuit Card ID (ICCID) is displayed for devices that have no SIM card inserted.
  • In Secure Hub for Android, the installed mobile productivity apps are not displayed on the My Apps screen upon restarting the device.
  • In Secure Hub for Android, you are unable to unlock Android Enterprise devices if you’ve entered the wrong password multiple times and try restarting the device. The following error message appears: Phone turned off, Contact your IT administrator.

Secure Hub 21.2.0

Secure Hub for Android

Known issues in Secure Hub 21.2.0

In Secure Hub for Android, the installed mobile productivity apps do not appear on the My Apps screen upon restarting the device.

Fixed issues in Secure Hub 21.2.0

  • Secure Hub for Android hangs during enrollment of devices.
  • On certain versions of Secure Hub for Android, the Home and Back buttons are not visible once enrollment is complete on Samsung Knox devices.

Secure Hub 21.1.0

Known issues in Secure Hub 21.1.0

There are no known issues in this release.

Fixed issues in Secure Hub 21.1.0

  • On devices running Android, Secure Hub fails to connect to Citrix Endpoint Management when the Connection scheduling device policy is enabled.
  • On certain registered Samsung devices, the wrong serial number is reported on the Citrix Endpoint Management console.

Secure Hub 20.12.0

Known issues in Secure Hub 20.12.0

There are no known issues in this release.

Fixed issues in Secure Hub 20.12.0

  • In Secure Hub for iOS, you are unable to enroll your devices. You get the following error: Your device isn’t enrolled.
  • In Secure Hub for iOS, the user agent string doesn’t include the OS version for devices enrolled in the MAM+MDM.
  • On Android Enterprise devices, Secure Hub crashes during enrollment.
  • Secure Hub for Android version 20.11.0 crashes on certain Samsung devices.

Secure Hub 20.11.0

Secure Hub for Android

Known issues in Secure Hub 20.11.0

There are no known issues in this release.

Fixed issues in Secure Hub 20.11.0

On some Samsung devices, Secure Hub for Android crashes, and you get the following error: Secure Hub keeps stopping.

Secure Hub 20.10.5

Known issues in Secure Hub 20.10.5

There are no known issues in this release.

Fixed issues in Secure Hub 20.10.5

  • On corporate-owned single-use (COSU) devices running Android 11, you can't set Secure Hub as the default launcher.
  • On devices running Android, the creation of a work profile fails on certain Samsung devices. You get the following error: Unable to configure work profile.
  • The mobile app management (MAM) enrollment of Android devices fails through the Citrix Endpoint Management AutoDiscovery Service.
  • On devices running iOS, you can’t launch certain apps. You get the error Please update Secure hub to use this app even when there’s no update available for Secure Hub.
  • On devices running iOS, Secure Mail prompts for authorization after the maximum offline period expires. Secure Mail then switches to Secure Hub, preventing you from using it.

Secure Hub 20.9.0

Known issues in Secure Hub 20.9.0

There are no known issues in this release.

Fixed issues in Secure Hub 20.9.0

  • In Secure Hub for iOS, when certificate pinning is enabled, connections are established across servers even if the certificate pinned from one of the servers is incorrect.
  • In Secure Hub for iOS, you can’t receive notifications. You get the following error: There are no devices with a valid Secure Hub token.

Secure Hub 20.7.5

Known issues in Secure Hub 20.7.5

On corporate-owned single-use (COSU) devices running Android 11, you can't set Secure Hub as the default launcher.

Fixed issues in Secure Hub 20.7.5

  • In Secure Hub for Android, enrolling Android devices fails when certificate pinning is enabled.
  • In Secure Hub for Android, the Date Time Change feature in the Restrictions policy does not work on Samsung devices.
  • In Secure Hub for Android, the firewall policy doesn't work on Samsung devices running versions 19.12.5 and later.
  • In Secure Hub for Android, you are unable to uninstall apps from My apps.

Secure Hub 20.6.5

There are no known or fixed issues in this release

Secure Hub 20.3.0

Secure Hub for iOS

There are no known or fixed issues in this release.

Secure Hub 20.2.0

Secure Hub for iOS

Known issues in Secure Hub 20.2.0

There are no known issues in this release.

Fixed issues in Secure Hub 20.2.0

  • In Secure Hub for iOS, Mobile Application Management (MAM) enrollment fails on a few iOS devices.
  • In Secure Hub for iOS, apps are being removed randomly from devices.

Secure Hub 20.1.5

There are no known or fixed issues in this release.

Secure Hub 19.12.5

Known issues in Secure Hub 19.12.5

There are no known issues in this release.

Fixed issues in Secure Hub 19.12.5

On devices running iOS 13, the user certificates for XenMobile® Server are checked and renewed on the actual expiration date rather than relying on the SSL error code to check user certificate expiration.

Secure Hub 19.11.5

Known issues in Secure Hub 19.11.5

There are no known issues in this release.

Fixed issues in Secure Hub 19.11.5

In Secure Hub for iOS, enrollment fails for MDX wrapped apps after disabling user entropy.

Secure Hub 19.10.5

Secure Hub for Android

Known issues in Secure Hub 19.10.5

There are no known issues in this release.

Fixed issues in Secure Hub 19.10.5

In Secure Hub for Android, you are unable to install business apps on devices running Secure Hub version 19.10.5 when the Credentials policy is configured.

Secure Hub 19.10.0

Known issues in Secure Hub 19.10.0

  • In Secure Hub for Android, enrollment of Google Pixel 2 devices running on Android version 10 in Device Owner mode fails due to permission failure.
  • In Secure Hub for Android, on Google Pixel devices running Android version 10, enrollment of devices in Device Owner mode fails due to failure in validating the location permission.

Fixed issues in Secure Hub 19.10.0

There are no fixed issues in this release.

Secure Hub 19.9.5

There are no known or fixed issues in this release.

Secure Hub 19.9.0

Known issues in Secure Hub 19.9.0

In Secure Hub for Android 19.9.0 with Android Enterprise enabled, the following issue occurs on Pixel 2 devices: The Credentials policy does not deploy successfully. As a result, users are not prompted for a certificate along with a password and a certificate is not installed. As a workaround, users can manually refresh their policies in the app from Preferences > Device Information. From there, they press Refresh policy, enter their credentials, and confirm the success message.

Fixed issues in Secure Hub 19.9.0

There are no fixed issues in this release.

Secure Hub 19.8.5

There are no known issues or fixed issues in this release.

Secure Hub 19.8.0

Known issues in Secure Hub 19.8.0

In Secure Hub for iOS, when you enter an incorrect password on a shared device, and tap Switch user to log in again, the Please wait message appears indefinitely.

Fixed issues in Secure Hub 19.8.0

The Mobile Device Management network is incorrectly routed when connected through the full VPN.

Secure Hub 19.7.5

Known issues in Secure Hub 19.7.5

There are no known issues in this release.

Fixed issues in Secure Hub 19.7.5

  • In Secure Hub for Android, prompts to install web clips appear rapidly, interfering with the configuration of the Secure Hub PIN.
  • On Samsung Knox devices version 3 and higher, when you enroll Secure Hub in Profile Owner mode and push Samsung MDM license key policy for the Android Enterprise platform, the Device Container Password Reset command fails.
  • The following error appears in Secure Hub for iOS when you attempt to configure a Public App in the MAM mode by using the new app URL from the Apple Store: Couldn't Load Store. Please try again. Refer to the workaround in https://support.citrix.com/article/CTX256704.
  • In Secure Hub for Android, you are unable to install MDX apps when a full VPN tunnel is established.
  • When a session time-out occurs on Point Mobile PM80 devices running Secure Hub for Android in the Shared Devices mode, you are unable to log in again.
  • In Secure Hub for Android, you get the following error after installing and launching internally wrapped applications: The way that your data is encrypted in this app has changed. Please delete this app and reinstall it.

Secure Hub 19.6.5

Known issues in Secure Hub 19.6.5

There are no known issues in this release

Fixed issues in Secure Hub 19.6.5

  • On devices running iOS, Secure Hub does not load the store when there is a Global Server Load Balancing failover.
  • In Secure Hub for Android, the Refresh policy fails. As a result, you are unable to deploy any new device policies.
  • In Secure Hub for Android, enrollment or Refresh policy actions on Samsung S10 devices take a long time.
  • On devices running Android, non-managed apps lose connectivity when Secure Hub establishes a full VPN connection.

Secure Hub 19.5.5

Known issues in Secure Hub 19.5.5

  • In Secure Hub for Android, devices in Corporate Owned Single Use (COSU) mode lose connectivity after few minutes of enrollment, and do not receive notifications even with GCM enabled.
  • When you deploy the Location policy on devices, at a time, for both Profile Owner and Device Owner modes, the user account in Device Owner mode is deleted. This issue occurs during NFC bump enrollment and when Endpoint Management is configured in the MDM mode.

Fixed issues in Secure Hub 19.5.5

  • From this release, Secure Hub only supports devices running Android 5.0 and later.
  • In Secure Hub for Android, enroll a device in device owner mode and set a new password. The device is not locked in the first attempt.

Secure Hub 19.5.0

Known issues in Secure Hub 19.5.0

  • After enrollment, devices OnePlus Android version 7.1.1 and OnePlus 5T Android version 9.0.3 require manual restart of Secure Hub to be prompted for Citrix PIN.
  • In Secure Hub for Android, required apps are not deployed on Android devices unless you refresh the policy or refresh the store.

Fixed issues in Secure Hub 19.5.0

  • From this release, Secure Hub only supports devices running Android 5.0 and later.
  • In Secure Hub for Android, Android 6.0 devices fail to enroll if multiple subject alternative names are present in the server certificate.
  • In Secure Hub for Android, managed apps are not uninstalled after disenrollment of devices.
  • On Samsung S9 devices, after users update to Android P, the following issue occurs: When you change the device password via Endpoint Management, the password on the device is not changed. Instead the screen turns black and the Endpoint Management console shows a locked device status.

Secure Hub 19.4.5

Known issues in Secure Hub 19.4.5

There are no known issues in this release.

Fixed issues in Secure Hub 19.4.5

On iOS devices, when you click the device enrollment link, the Endpoint Management FQDN instance name is not auto-populated in Secure Hub. The device enrollment request fails.

Secure Hub 19.3.5

Known issues in Secure Hub 19.3.5

When notifications are sent from Secure Hub for iOS, the notification badge count is not updated for Secure Hub.

Fixed issues in Secure Hub 19.3.5

  • In Secure Hub for Android, when you enroll shared devices, deploy the Webclip policy and add web and SaaS apps, the deployment is successful. However, this deployment appears as failed in the App inventory screen in the Citrix Endpoint Management console.
  • In Secure Hub for Android, when users log in with secure PIN, a VPN tunnel is established, but Secure Web does not load any website. However, the website loads as expected when Secure Web is closed and reopened.
  • Secure Mail for Android configured with Microsoft Intune policies returns a blank screen after authentication.
  • In Secure Hub for Android, apps that have disabled encryption are attempting to obtain encryption keys from Secure Hub.
  • Secure Mail for Android crashes at launch when Intune Company Portal version 5.0.4324.0 is installed.
  • In Secure Hub for Android, you are unable to use the system apps on corporate owned single use (COSU) Android Enterprise devices running on Android 7.1.1.
  • In Secure Hub for Android, when you configure multiple apps from Google Play as Required apps and try to enroll, you are prompted to install the first app. The initial prompt is immediately followed by another prompt to install the second app and so on.

Secure Hub 19.3.0

Known issues in Secure Hub 19.3.0

  • In Secure Hub for Android, when you enroll shared devices, deploy the Webclip policy and add web and SaaS apps, the deployment is successful. However, this deployment appears as failed in the App inventory screen in the Citrix Endpoint Management console.
  • On Android Enterprise devices, when a lock action is set for geofence breach in the Location policy, the device prompts you to set a new passcode instead of using the system generated passcode.

Fixed issues in Secure Hub 19.3.0

Locking fully managed Android Enterprise devices remotely using the Lock with passcode security action might fail without notifying you of the failure. To ensure a device is locked, set Lock with passcode twice. The device is locked with the second passcode you set.

Secure Hub 19.2.0

Known issues in Secure Hub 19.2.0

There are no known issues in this release.

Fixed issues in Secure Hub 19.2.0

  • In Secure Hub for iOS, the following SSL handshake failure message appears repeatedly when users log off from Secure Hub store: Network request to fetch apps is timed out from Server.
  • The Files device policy for Android Enterprise does not deploy to Android devices in work profile mode.
  • In Secure Hub for Android, the login authorization for a new user takes a long time on shared devices. When you log off as an enrolled user and try to login as a new user, Secure Hub keeps loading until you reboot the device.
  • In Secure Hub for Android, cloud customers are unable to enroll Android Enterprise devices with an external identity provider.
  • In Secure Hub for Android, when you are in Corporate Owned Single Use (COSU) mode, the app icons are overlapped in Secure Hub.
  • In Secure Hub for Android, when certificate pinning is enabled for your existing setup, the authentication fails and returns to the first-time user screen when the certificate has multiple Subject Alternative Names.

Secure Hub 19.1.5

Known issues in Secure Hub 19.1.5

  • In Secure Hub for Android, when you update password due to password policy change, the badged apps do not appear on Samsung Galaxy S8 devices.
  • In Secure Hub for Android, the Files device policy Android Enterprise does not deploy to devices in work profile mode.

Fixed issues in Secure Hub 19.1.5

  • In Secure Hub for Android, when users log in with Secure PIN a VPN tunnel is established, but Secure Web does not load any website. However, the website loads as expected when Secure Web is closed and reopened.
  • In Secure Hub for Android, when you log on with Secure PIN a VPN tunnel is established, but Secure Web does not load any website. However, the website loads as expected when Secure Web is closed and reopened.
  • In Secure Hub for Android, when you try to capture logs of the in-house app called TechXpert, Secure Hub restarts and asks you to reauthenticate.

Secure Hub 19.1.0

Known issues in Secure Hub 19.1.0

In Secure Hub for iOS, when you deploy an MDX and web or SaaS apps, they appear in My Apps screen. When you tap More, a popup appears with Delete and Cancel options that have the format of old UI branding.

Fixed issues in Secure Hub 18.12.0

  • On Samsung Knox devices enrolled for Android For Work, when the password policy is configured to expire in one or two days, the Password Expired message appears repeatedly.
  • You are unable to enroll OnePlus 5T devices for Android Enterprise using the QR code enrollment method.

Secure Hub 18.11.0

Fixed issues in Secure Hub 18.11.0

  • You are unable to perform single sign-on on Android devices enrolled in the Shared Device mode. The following error appears: Your corporate credentials cannot be retrieved at this time. Manual login to ShareFile is blocked due to admin policy.
  • You cannot edit Android volume levels on corporate-owned, single-use (COSU) devices.

Secure Hub 18.10.5

Fixed issues in Secure Hub 18.10.5

  • If you have FIPS mode enabled in XenMobile Server, after users update Secure Hub for iOS to version 18.10.5, an encryption-related error message appears when users open apps.

Secure Hub versions 10.8.25 to 18.10.6

Fixed issues in Secure Hub versions 10.8.25 to 18.10.6

  • Secure Hub versions 10.8.25 to 18.10.6 (Android) include no known issues. The following issues are fixed in Secure Hub. The list includes issues with MDX that affect Secure Hub.

Secure Hub 18.10.0

Fixed issues in Secure Hub 18.10.0

  • If the MVPN policy is turned off in the EMS console, Secure Hub displays a blank screen when trying to open Intune managed apps.

Secure Hub 10.8.60

Fixed issues in Secure Hub 10.8.60

  • On Samsung Galaxy Tab Active 2 SM-T395 devices, the Full Wipe security action fails for Secure Hub for Android when admins set a Disable Factory Reset restriction in XenMobile.
  • Secure Hub for Android becomes unresponsive during enrollment of devices when the VPN policy is configured and the Citrix SSO application is not installed on the device. It becomes responsive if you tap the Back button or restart the app.
  • Secure Hub for Android crashes during enrollment in the Device Owner mode in an Android Enterprise environment.
  • After users enter a valid PIN for Secure Hub for iOS, Secure Hub prompts users for the PIN repeatedly.
  • Secure Hub for Android crashes during enrollment in the Profile Owner mode in an Android Enterprise environment.
  • Using Android Enterprise in Secure Hub for Android installs Google Chrome by default.
  • Upgrading Secure Hub for iOS to version 10.8.55, doesn't allow existing or new iOS device enrollments.

Secure Hub 10.8.55

Fixed issues in Secure Hub 10.8.55

  • Users cannot sign on to Secure Hub to enroll in Android for Work accounts when the G Suite credentials differ from the credentials in Endpoint Management.

Secure Hub 10.8.55

Known issue in Secure Hub 10.8.55

  • After removing your Secure Hub account from your device, MDM re-enrollment fails.

Secure Hub 10.8.50

Known issue in Secure Hub 10.8.50

  • On Secure Hub for Android, users cannot add a web link shortcut.

Secure Hub 10.8.35

Fixed issues in Secure Hub 10.8.35

  • On Android O, shortcuts created by policies do not appear on the device home screen. This behavior is by design in Android O.
  • On Android, Secure Hub does not open on Samsung tablets after a period of inactivity.
  • In Secure Hub for Android, you are unable to deploy the push policy on Samsung Knox devices.
  • In Secure Hub for iOS, occasionally the following issue occurs: After users change their Active Directory password, they must keep entering their PIN in a loop.

Secure Hub 10.8.25

Fixed issues in Secure Hub 10.8.25

  • For third-party iOS Cordova apps wrapped with the MDX Toolkit version 10.7.20, a black screen appears instead of a PIN screen after you enable the Obscure screen contents policy.
  • On Zebra T51 devices running Android 7, users cannot install the Citrix Launcher app.

Secure Hub 10.8.20

Fixed issues in Secure Hub 10.8.20

  • After users update their Android devices to version 8 (Oreo): They cannot install enterprise or .apk apps from the app store that you deploy from Endpoint Management. Even when they enable installation of third-party apps, the issue persists. The issue is not limited to Samsung devices.

Secure Hub 10.8.15

Fixed issues in Secure Hub 10.8.15

  • Secure Hub for Android crashes while fetching location details on devices running Android O.

Secure Hub 10.8.10

Fixed issues in Secure Hub 10.8.10

  • On Android devices, when multiple apps do not install automatically or users don't click Install themselves, the apps keep downloading. As a result, high data usage occurs.
  • On devices running Android 7 or later: When you send a lock security action with a password to the device from XenMobile Server, the device locks. However, the device password does not change if users have an existing lock screen password. Users can use the original passcode to unlock the device.
Secure Hub for iOS update on March 19, 2018: Secure Hub version 10.8.6 for iOS is available to fix an issue with the VPP app policy.