Closed frpaf closed 6 months ago
Please read the exit criteria for the App Configuration section of our docs. App configuration can be configured for managed apps (as shown in your screenshots) or for managed devices.
To receive managed app config, the user must be MAM-enrolled (see MAM integration essentials).
To receive managed device config, the device must be enrolled (see Enroll Android devices).
Intune Android App SDK Policy Enforcement Issue
Questions to Ask Before Submission
Summary
Each phase of the [Intune App SDK for Android Integration Guide] outlines specific exit criteria for proceeding to subsequent phases.
Please reference the specific exit criteria scenario that is failing.
Repro Steps
A copy of the source project with the issue is available at
https://github.com/franferns/intune-app
Please provide concrete steps to reproduce the issue you are encountering.
Integrating the intune sdk creating a folder in the app folder with MAMSDK with
Making changes to the root build.gradle file
Making changes to app/build.gradle file adding reference to the sdk aar file
and the settings.gradle file.
And then the code for accessing the config from the
The app configuration policy configured is as follows![image](https://github.com/msintuneappsdk/ms-intune-app-sdk-android/assets/129268891/5492bf69-e3bf-4636-958e-d3b91569395e)
Expectation: To be able to read configured values app config policy "CustomerURL" the value returned is null . Shown as a toast message.
Observation: The code where we get an instance of the MAMAppConfig returns a object even on an non company portal device . Isnt it suppose to return null for no work profile (non company portal) related devices.
Details
A copy of the source project with the issue is available at
https://github.com/franferns/intune-app