Forum Discussion
ANDROID 15: Problem with unlock code expiry in COPE mode
Hello,
Our users' Samsung smartphones are enrolled in Intune in COPE mode. We have a configuration profile that requires a device unlock code with an expiration time. We haven't configured a code for the work profile, so the One Lock setting is enabled by default.
In Android 15, following the expiration of the unlock code, the user is now required to change the unlock code. However, once they do so, when they launch an app in the work profile, the smartphone also asks them to change the work profile code.
I don't understand why the smartphone is asking to change the work profile code when the One Lock setting is enabled.
Is anyone else having the same problem?
Benjamin
Hello,
Samsung confirmed to me that the problem is resolved in Android 16. I've run several tests on Android 16 and indeed, I haven't been able to reproduce the problem.
Samsung hasn't given me any information on the cause of this issue.
12 Replies
Hi Benjamin - just wanted to let you know that I've asked our team to look into this and I'll get back to you as soon as I hear back from them.
In the meantime, I'm adding some of our expert members to see if they can help you out -
Moombas , jasonbayton, Michel , Alex_Muc, Rakib thanks in advance for your insights 🤞
Hi Benjamin,
I haven't heard this issue before, what do you mean with one lock setting? I don't recognize that as an API in Intune.
Hi Michel,
The "One Lock" setting available in the settings allows you to unlock your work profile with your smartphone's PIN.
Unlocking thesmartphone also unlocks the work profile.
ah thanks, wasn't aware of its name but I now see in the settings what you mean.
Couple things I would check first:
- Did you confirm wether or not the one lock setting is still enabled?
- What happens if you disable and enable it?
- Do you have policies in an OEMconfig that might interfere with this?
I have a Samsung in COPE myself, on Android 15 managed in Knox Manage and it has no such issues. Same for most of our Samsung customers. So my first guess would be a conflict between policies on the device. Or a firmware bug.
Do you run KAI? If so, you could use it to easliy extract a debug log to share with Samsung support via your Knox portal. Its free of charge support.
Hi , after extensive testing and discussions with Samsung, they informed me that R&D had found the cause of the problem. I don't have any details on the cause or the resolution timeframe, but it's encouraging.
Hello,
Samsung confirmed to me that the problem is resolved in Android 16. I've run several tests on Android 16 and indeed, I haven't been able to reproduce the problem.
Samsung hasn't given me any information on the cause of this issue.
