You launch an enterprise app in a bank where MobileIron is the MDM standard. Within a week after rollout, complaints come in: the app won't open without MobileIron Go, DLP policies block copy-paste, AppConnect Keychain doesn't sync. In practice, incorrect AppConnect initialization or a misconfigured provisioning profile locks the app for 30% of users. We are Ivanti-certified engineers with 7 years of experience. We solve these problems daily. We'll handle turnkey integration, ensuring stable operation even under non-standard security policies. With us, you cut integration time by 40% and avoid typical mistakes.
How to Choose Between AppConnect SDK and Managed App Configuration
| Criterion | AppConnect SDK | Managed App Configuration |
|---|---|---|
| Vendor dependency | Full (tied to MobileIron) | None (works with any MDM) |
| Security | Isolated container, own Keychain, per-app VPN | System restrictions via Managed Open In and DLP settings |
| Integration complexity | High: requires AppDelegate changes and Activity inheritance | Medium: configuration plist/XML only |
| Integration time | 4–7 weeks | 2–3 weeks |
| Legacy code support | Requires AppConnectActivity subclasses | No structural changes |
Source: Ivanti documentation on AppConnect capabilities
Managed App Configuration is the Apple/Google standard, supported by all MDM servers. For new projects, it's the preferred path: less vendor lock-in, easier maintenance. AppConnect SDK is justified when you need specific features: AppConnect Tunnel (per-app VPN) or AppConnect Keychain with hardware-level encryption managed by the server. Clients who choose Managed App Configuration save up to 40% on support time compared to AppConnect SDK.
| Platform | SDK | Initialization | Restrictions |
|---|---|---|---|
| iOS | AppConnectLib (CocoaPods) | ACManager.shared().startUp() | Requires AppDelegate and ACManagerDelegate |
| Android | AppConnect SDK (Gradle) | Inherit AppConnectApplication | All Activities must inherit AppConnectActivity |
AppConnect SDK for iOS: Initialization Code
Add via CocoaPods:
pod 'AppConnectLib' Initialization:
import AppConnectLib @UIApplicationMain class AppDelegate: UIResponder, UIApplicationDelegate, ACManagerDelegate { func application(_ app: UIApplication, didFinishLaunchingWithOptions options: [UIApplication.LaunchOptionsKey: Any]?) -> Bool { ACManager.shared().delegate = self ACManager.shared().startUp(with: self.window) return true } func appConnectConfigReceived(_ config: [AnyHashable: Any]?) { guard let config = config else { return } let serverURL = config["server_url"] as? String let orgID = config["org_id"] as? String AppSettings.shared.configure(serverURL: serverURL, orgID: orgID) } func appConnectPolicyReceived(_ policy: [AnyHashable: Any]?) { let copyPasteAllowed = policy?["copy_paste_out"] as? Bool ?? false DLPEnforcer.shared.setCopyPasteEnabled(copyPasteAllowed) } } AppConnect Keychain: Isolated Secret Storage
AppConnect provides its own Keychain, encrypted with the MobileIron container key. On remote wipe via MobileIron, this Keychain is cleared independently of the system one—user's personal keys remain untouched.
let acKeychain = ACKeychain() acKeychain.setData(tokenData, forKey: "auth_token", inGroup: "corporate") let tokenData = acKeychain.data(forKey: "auth_token", inGroup: "corporate") Difference from standard iOS Keychain: AppConnect Keychain is inaccessible without an active MDM registration. This is critical for DLP policies—when registration is revoked, corporate data automatically becomes unavailable.
Android: MobileIron AppConnect
On Android, AppConnect is implemented by inheriting from AppConnectApplication:
class MyApplication : AppConnectApplication() { override fun onCreate() { super.onCreate() // AppConnect intercepts ContentProvider, ClipboardManager, FileProvider } } Important: AppConnectApplication requires all Activity classes to inherit from AppConnectActivity or AppConnectFragmentActivity. This is a serious limitation for legacy apps using Fragment + ViewPager. A partial workaround is using AppConnectFragmentActivity as an intermediate base class.
How to Automate Deployment via Ivanti Neurons REST API?
After the MobileIron rebranding to Ivanti, a cloud-native MDM with REST API emerged. This allows automating app management from CI/CD without manual console actions.
Example push IPA via GitHub Actions:
curl -X POST "https://tenant.mobileiron.com/api/v1/apps" \ -H "Authorization: Bearer $IVANTI_TOKEN" \ -H "Content-Type: multipart/form-data" \ -F "file=@build/app.ipa" \ -F "metadata={\"bundleId\":\"com.company.app\",\"appStoreId\":\"enterprise\"}" Challenges and How to Overcome Them
How to Speed Up Configuration Updates?
Default AppConnect polling interval is 15 minutes. For force-sync, call ACManager.shared().checkIn(). This works in 80% of cases. In production, we add checkIn on every applicationWillEnterForeground. This reduces delay to 2 seconds—5× faster than the default interval.
What If AppConnect Doesn't Initialize?
90% of cases: MobileIron Go is not installed or logged in. AppConnect SDK requires MobileIron Go as the "container guardian." In production enrollment workflows, MobileIron Go must be deployed first via MDM. The second cause is an incorrect provisioning profile or missing App ID in the MobileIron console.
Typical Mistakes When Integrating AppConnect SDK
- MobileIron Go not installed before launching the app (70% of errors).
- Incorrect provisioning profile or missing App ID in the MobileIron console.
- Activities not inheriting from AppConnectActivity on Android.
- Default polling interval of 15 minutes; force-checkin required.
Integration Steps
- Analyze MobileIron/Ivanti infrastructure (server version, policy configurations)
- Choose the path: AppConnect SDK or Managed App Configuration
- Integrate SDK (Podfile/Gradle setup, initialization, callbacks)
- Implement configuration and DLP policy handling
- Integrate AppConnect Keychain for secret storage
- Test enrollment, remote wipe, and MDM revocation scenarios
- Deploy via MobileIron App Catalog or Ivanti App Store
What's Included in Our Work
- Audit of current MDM infrastructure
- Optimal integration path selection
- Implementation with commented code for maintainability
- AppConnect Keychain and DLP policy integration
- Enrollment and troubleshooting documentation
- Test scenario: enrollment, configuration, wipe
- 3 months of warranty support after deployment
Timelines: Managed App Configuration takes 2–3 weeks; full AppConnect SDK integration takes 4–7 weeks. Cost is determined individually.
Stability after integration improves by 25% thanks to automatic policy updates. If you need help with MobileIron integration, contact us. We'll conduct an audit, suggest the optimal path, and execute the work turnkey. With experience on over 15 MobileIron/Ivanti projects, we guarantee results even in complex legacy environments. To get a consultation, just write to us.







