Troubleshooting
Official Troubleshooting Guide#
Refer first to Microsoft's official troubleshooting documentation to find solutions to common issues.
Additionally, for authentication issues, the Sign-in logs section of the Azure Active Directory app registration portal often has helpful error messages that point to Azure-side configuration issues. Please contact your administrator for access to this resource in Azure.
iOS#
"Unexpected failure" when performing brokered auth#
This error is the same as the one mentioned in this issue.
To fix it, some additional configuration for MSAL is required. Make sure you've added the following line inside of the CFBundleURLSchemes as shown below to your Info.plist to enable using the authenticator app:
<key>CFBundleURLTypes</key> <array> <dict> <key>CFBundleURLSchemes</key> <array> <!-- The important line --> <string>msauth.$(PRODUCT_BUNDLE_IDENTIFIER)</string> </array> </dict> </array>This enables your app to launch the authenticator.
MSALErrorDomain -50000 when using brokered auth#
This is a configuration issue in the Azure Active Directory Portal. Ensure the app registration has permission to access the Microsoft Mobile Application Management API. Please contact your administrator to enable your app to access the necessary APIs.
Another thing to try is setting AutoEnrollOnLaunch to 1 in the IntuneMAMSettings in Info.plist.
Build error: Undefined symbols and 12.0 deployment target warning#
If you see this error:
The issue could be not setting the minimum deployment target for your App to 12.2 or above or the Podfile extra script to disable bitcode in all targets was not added.
See the iOS Installation guide and follow the deployment target and Podfile recommendations to resolve the issue.
Enable logging#
Android#
com.microsoft.identity.client.exception.MsalClientException: The redirect URI in the configuration file doesn't match#
The error com.microsoft.identity.client.exception.MsalClientException: The redirect URI in the configuration file doesn't match with the one generated with package name and signature hash. Please verify the uri in the config file and your app registration in Azure portal. is thrown when attempting to authenticate using acquireToken or loginAndEnrollAccount.
This issue is thrown because the hash used for your redirect uri in auth_config.json and/or AndroidManifest.xml isn't correct. Follow the Android installation guide to find and set the correct hash for your app.
Gradle sync error: Null extracted folder for artifact#
This happens when the reference to the Intune App SDK for Android AAR file (Microsoft.Intune.MAM.SDK.aar) cannot be found.
android.content.pm.PackageManager$NameNotFoundException com.azure.authenticator#
This error happens on Android 30 when your AndroidManifest.xml is missing <queries> for the Microsoft Authenticator or Intune Company Portal apps.
This is a new Android security feature (as of Android 30) that restrict the app to query for only a defined set of external apps.
To fix this issue, follow the Android install guide for the AndroidManifest.xml instructions to ensure the proper <queries> definition has been added.
Direct local .aar file dependencies are not supported when building an AAR.#
This compilation error can happen with versions of the plugin 2.4.1 and below. Update to the latest version then open the build.gradle file for the Module: android.app and ensure it contains the following line in dependencies:
dependencies { ... implementation files("../../node_modules/@ionic-enterprise/intune/android/ms-intune-app-sdk-android/Microsoft.Intune.MAM.SDK.aar")}java.lang.ClassNotFoundException: Didn't find class "com.ionicframework.intune.IntuneApplication"#
This runtime error can occur if you have forgotten to add the following line to the dependencies of the build.gradle file for the Module: android.app:
dependencies { ... implementation files("../../node_modules/@ionic-enterprise/intune/android/ms-intune-app-sdk-android/Microsoft.Intune.MAM.SDK.aar")}