Forum Discussion
ANDROID 15: Problem with unlock code expiry in COPE mode
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.
After changing the smartphone's unlock code, if you launch an app in the work profile, the system asks you to create an unlock code for the work profile. You can't access work apps until you set one.
Once the work profile code is set, the "One Lock" setting is disabled. It's possible to re-enable it to have only one code, but it's not easy for users (they also have to remember the code they set for the work profile).
We use KSP, but there are no rules regarding passcodes.
It's strange; I set the code expiration to 1 day, and this morning I didn't have the problem, even though I've reproduced it several times before on this tablet.
I have over 40 incidents reported by users for this issue, always on Android 15, but it doesn't seem to affect everyone. I will continue my tests and I will take logs when I reproduce the problem.
Feels like a bug somewhere. Since you use KSP I assume you have a Knox tenant as well? If so, create a support ticket via Knox. You well get support from your local Samsung team and they can assist with this.
If it really is a bug, they are able to make adjustments in firmware or with the MDM vendor to fix this together with you.
Today I reproduced the problem, took the logs and created a case to Samsung ETS support. I hope they can help me.
