---
title: Limitations
slug: mobileatwork/ios/release-notes/limitations
createdAt: 2026-11-17T15:35:40.547Z
---

These are cumulative release notes. If a release does not appear in this section, then there were no associated limitations.

:::ExpandableHeading
## Ivanti Mobile\@Work 12.12.30 for iOS - Limitations

- **1382950:** Non-App Store Signer (NASS) threats are not detected on iOS 17.5 and above devices.
  **Workaround:** None
:::

:::ExpandableHeading
## Ivanti Mobile\@Work 12.12.20 for iOS - Limitations

- **1382950:** Non-App Store Signer (NASS) threats are not detected on iOS 17.5.x devices.
  **Workaround:** None
:::

::::ExpandableHeading
## Ivanti Mobile\@Work 12.11.110 for iOS - Limitations

- **IOS-18438:** Safari content blocker does not support whitelisting. If the Ivanti content blocker extension is enabled in Safari settings, phishing URLs that the device user has manually allowed remain blocked. A ticket has been filed with the vendor.
  **Workaround:** None
- **IOS-18250:** MTD status is not changing to an error state when admin sets the wrong Lookout MTD activation key: The Lookout SDK keeps working even when the Enrollment Code becomes invalid.
  **Workaround:** None
- **IOS-18575:** Upon disabling Content Protection on the Ivanti EPMM server, the Lookout Secure DNS profile still displays in iOS devices > Settings.
  **Workaround:** None
- **IOS-18576:** Devices are not protected from phishing attacks when the following are configured on the devices:
  - Third-party VPNs
  - Third-party DNS

:::Paragraph{indent="2"}
**Workaround:** None
:::
::::

:::ExpandableHeading
## Ivanti Mobile\@Work 12.11.100 for iOS - Limitations

- **IOS-18346:** Due to Apple's design limitations, Ivanti Mobile\@Work may be shortened to three dots at the end and have spaces removed on certain devices.
  **Workaround:** None
- **IOS-18228:** After upgrading the Ivanti Mobile\@Work client, the Mobileiron logo/icons may continue to display due to caching.
  **Workaround:** To refresh the screen/cache, simply swipe the screen after the Ivanti Mobile\@Work client upgrade and the cache may be cleared.
:::

:::ExpandableHeading
## Ivanti Mobile\@Work 12.11.90 for iOS - Limitations

- **IOS-18097:** For DT Client, "Imprint" is not localized in Italian, Chinese, or Spanish.
  **Workaround:** None.
:::

:::ExpandableHeading
## Ivanti Mobile\@Work 12.11.80 for iOS - Limitations

- **IOS-17703:** GCC and DoD Tenant types are not supported for Azure Device Compliance feature by branded clients.
  **Workaround:** None.
:::

:::ExpandableHeading
## Ivanti Mobile\@Work 12.11.71 for iOS - Limitations

- **IOS-17628:** During enrollment, Lockdown should be tuned off while installing the MDM profile. Once the device has been successfully enrolled and the MDM profile was successfully installed, the device user can enable Lockdown again.
:::

:::ExpandableHeading{customAnchorSlug="Mobile@W"}
## Ivanti Mobile\@Work 12.11.52 for iOS - Limitations

- **APG-1208:** For iOS 15 devices, unable to install Mobile\@Work on the device after signing the app.
  **Workaround:** Applications that were signed on macOS 10.15 "Catalina") or older should be re-signed using macOS 11.x ("Big Sur") or newer. For more information, see article: [iOS 15: In-House / Enterprise Apps Fail to Install](https://forums.ivanti.com/s/article/iOS-).
- **IOS-17330:** When anti-phishing is enabled, VPN sometimes turns off while browsing on a cellular network. This could cause issues while browsing and downloading apps.
- **IOS-17329:** When anti-phishing is enabled on the device, App download and page loading sometimes fails.
  **Workaround:** Turn off and then turn on the VPN to fix the issue.
:::

:::ExpandableHeading{customAnchorSlug="Mobile@W2"}
## Ivanti Mobile\@Work 12.11.40 for iOS - Limitations

- **IOS-16982:** On an iOS device with Azure Active Directory device compliance configuration, Microsoft shows Page not found error instead of non-compliance message when the device is out of compliance.
- **IOS-16100:** Device is not getting removed from the Microsoft Azure portal when device is de-registered from the Microsoft Authenticator portal. As a result, Microsoft 365 Access status is not getting updated on the device. There is no workaround for this issue.
:::

