Auto-Lock in web-app kiosk not working in iOS 15Solved

Participant
Discussion
3 years ago

I’d been using the Auto-Lock feature in the web-app kiosk policy for a while now. And since the last update, the feature is not working as expected. The device is not getting locked even after the specified time. Can someone update me on why this is happening?

Replies (7)

Marked SolutionPending Review
Participant
3 years ago
Marked SolutionPending Review

This could be an OS-specific issue. Have you tried updating your OS to the latest version iOS 15.1?

Marked SolutionPending Review
Participant
3 years ago
Marked SolutionPending Review

My devices are already updated to iOS 15.1.

Marked SolutionPending Review
Hexnode Expert
3 years ago
Marked SolutionPending Review

Hey Ulrika,

Thank you for reaching out to us!

We have taken this up and tested it on our behalf as well. After conducting thorough checks, our testing team has confirmed that this may be an OS-specific issue as it occurs only on devices running on iOS 15.1. This is not an issue on our end and it should be resolved when Apple releases newer updates for iOS devices. Make sure you update your devices as soon as the next update is released and check whether the issue has been resolved.

We will be having a check on this issue as well and will definitely get back to you in case of any positive updates. You can always get back to us if you have any further queries and we will be more than happy to help you out.

Hope I was able to clear your doubts.

Cheers!
Chris Coleman
Hexnode UEM

Marked SolutionPending Review
Participant
3 years ago
Marked SolutionPending Review

Sure, will install the next update as soon as it is released. Thanks for the update!

Marked SolutionPending Review
Participant
3 years ago
Marked SolutionPending Review

This issue seems to be fixed with iOS 15.2 update. Any confirmation on this?

Marked SolutionPending Review
Participant
3 years ago
Marked SolutionPending Review

I just tested it out on a device running on iOS 15.2. Auto-Lock is working fine now. It was only a version-specific issue.

Marked SolutionPending Review
Participant
3 years ago
Marked SolutionPending Review

That’s great!!