Posted on 02-16-2024 12:30 AM
New behaviour in iPadOS 17 - when you only define a lock screen wallpaper and do not define the home screen wallpaper and you do not click the check box to use the same image for lock and home, iPadOS 17 now magically makes home and lock screen identical. (Huh? That's not what I asked for)
I filed an Apple Feedback Assistant ticket and they said it is "currently functioning as intended".
It didn't do this in 16.
So what's the issue? If you make a reasonably great looking lock screen wallpaper it is totally distracting as a home screen wallpaper. The app icons become too cluttered with the background - there's no visual sense of depth to separate. If you use the QR code, it looks terrible on every page.
The consequence is that you have to allow changes to wallpaper and you have to choose a plain style home screen. Then if you want your beautiful lock screen to stay "locked" so that students don't remove it you have to play the restrictions dance in both Restrictions and the Wallpaper payload.
A bit of a step backward in 17.
Ideally, we need a feature where the lock screen can be define and locked down and let the user do what ever they like on the home screen. The payload definitions don't seem to support this real world use of background images.
More of a warning if you like badging your iPads, there are a few more steps than there used to be.
Posted on 08-26-2024 01:03 PM
I am currently running into this issue in that we have always set our devices with a student photo/ID number on the lock screen and then our district wallpaper as the home screen. Now, either it is inconsistently pushing a change to both, or we can't just go in after and correct one image, it changes both. This is unexpected Jamf behavior from how it behaved previously.