I am having this issue also, but I can't find how to access the page code injection for the lock page, so I don't know where to put this helpful code from @tuanphan. Can anyone help with this? Feels like a silly question...
I'm struggling with this right now. I tried this code and couldn't get it to work. The logo is bigger, but overlapping the headline. I inserted the full code, including the .sqs-slice-body part that should fix this problem, but it doesn't seem to change anything.
Thanks for the font size code. I will try that next. As for the original problem of spacing the logo/Title/body text, no, I haven't solved. When I increase the logo size, it overlaps with title and body text.
hi! @tuanphan i'm wanting to make the .gif on my homepage smaller. i've tried variations of the above from you + other sources but nothing makes a difference. could you help me make the gif much smaller? website danielle.earth
Hello, I've had the Pandora app for years and I've always had a "now playing" type banner in my status bar of my phone and my lock screen. I recently deleted and reinstalled Pandora and now that is gone and I can't figure out how to add it back. Any help? I have an LG thinq8 phone. Thank you!
I have the lg style 5. My lock screen stopped playing the banner after an android os update. Going to settings an the apps/ notifications option to select show all notification under lock screen options worked. I do one thi g different. My show all notifications option was already select and currently still not displaying the banner. I selected another option and then reselected show all notifications and its now working
Located this thread and followed the guidance to enable notifications for the app in the system menu, shut down Pandora and restarted the app - locked the phone and there it was!! Banner back baby. Thank you.
How can you do it ONLY for Pandora. I only see options to allow all notifications or none. I don't want text and email on my lock screen, but I really miss the music player for Pandora on there. Pixel 6Pro here. Thanks!
I've had Pandora for a while now and it use to be on my lock screen. My phone has the always on display so I could just tap it once and it would let me skip or pause songs. Well sometime last year it disappeared and I can't get it back. I've gone through my settings on both my phone and the app. I'm at a loss on why it's not there anymore. Any help would be great.
Also experiencing this. We are bound to AD, and do not use fast user switching. When the screen is locked, there is no username, only a password field which does NOT authenticate. This is very bad for us.
We are Jamf Connect, not bound but have fast user switching turned on. I am wonder since Apple is calling this a new lock screen if Jamf hasnt added the correct Configuration Profile parameters to Jamf Pro.
My production Apple silicon device this is not happening to, its connected to icloud and has a 2nd FV enabled user , i can see both and switch between them. but my Intel the issue is happening to is a single user that is FV enabled. it doesnt show the users name , just the icon and password field.
We're seeing something similar as well, but only seems to occur when enabled the Lock Screen is enabled via Apple > Lock Screen. If the device kicks off the screen saver and then locks, I'm still able to authenticate. This environment also has devices with a direct AD bind.
I have been experiencing this issue as well... based on some additional research, this appears to be a MacOS Sonoma issue, and not a Jamf issue as the same issue affects those with different MDMs. I just updated to 14.0(23A344) today and this seems to have resolved the issue. I believe this is still in Developer Beta, so I would assume it should roll out to the public pretty soon.
to anyone reading this, the issue is this: if you have "require passcode to unlock screen" turned on your config profile(security and privacy), but do not also have a screen saver policy(login window, options tab) set you will see this issue.
this isn't true. I just set a very basic profile without any passcode requirements and it fails. we have seen this as well with a brand new machine out of the box without being enrolled. The only thing that seems to be connected is whether or not the user has an AppleID signed in to the local user account that gets locked out. If you notice when the fail happens, ONLY when an Apple ID is signed in, will the lock screen show an icon for the local user and the AppleID icon supersedes the local user icon regardless of admin status. So it's almost like the system doesn't know what account to sign into when it goes to a lock state by way of screensaver or the lock screen being instantiated by pressing the TouchID button.
So, I was able to resolve it via JAMF. I set the screen lock timeout to 5 seconds, set screen saver to 15 minutes and in login items/mobility there are settings for local/network sync. Leave all of them unchecked. I think it's the lock screen/screen saver doing it.
My point is.. if I fixed it in JAMF, it's fixable locally. It's likely related to the settings I listed. Those are the only things I changed in a policy. Pre-policy update, no issue. Post policy update, issue. After policy fix, no issue.
I figured this out with Jamf support. In your Configuration Profile, if you need to have the key "Hide Admin Users" set to false. Also, if your Pre-Stage Enrollment, you need to have your local admin user not set to hidden as well. You also want to be sure local users are set to not be hidden. Those 3 things are what makes the lock screen work me as of 14.3. The other thing to check is that you don't have conflicting Configuration Profiles set for Login Window. Hope this helps!
Facing the same issues here, I was able to fix only one laptop by tinkering with the lock screen options from Name and Password to list of users, then restarting. I noticed the username and profile picture was back and allowed login. Unfortunately I couldn't replicate this on other computers though so the hunt continues.
I reached out to Jamf support and they wanted us to update to Jamf Connect 2.28.1 as 2.27 is the first version that fully supports Sonoma. Took some time to get approved to pilot the update and no good either. Lock screen issues persist. Emailed support back but I am starting to think it is an apple issue.
@clarkep I had a user have this same issue with (v29 jamf connect & macOS v14.1) Last week. Removed Login window and no issue as he had the issue for at least 2 days in a row , twice a day. Probably best work around yet. Side note - I was going to remove the payload anyways b/c of other Jamf Connect User sign screen oddities. Thanks for sharing.
So I understand that people have said this doesnt resolve the issue.. however Im posting this in a general reply because this 100% resolved the issue for me.
The reason Im here in this thread in the first place is because I was working on a new 802.1x policy. M2 Macbook Pro is the test device. The policy included 4 payloads: Certificate, Login Window, Mobility, Network.
Certificate: wifi cert thats 802.1x capable
Login Window: Window tab - show additional info, name and password text field, show shutdown
Options - disable auto login/apple id setup/siri setup, set computer name to record name - Screen saver was NOT set
Mobility - Account creation tab: Create mobile account at login with local home template and /bin/bash home directory
Network - personalized settings, however, use as a login window config, TTLS, PEAP, use directory auth, mschapv2 under protocols.
Thats it. Thats all that was in this policy. I applied it to the test device and started seeing this problem. Macbook would go to sleep, when you wake it up, only a password box and it doesnt accept your pw.
There was also a separate config policy that was a single security and privacy payload of Require Passcode to Unlock Screen. This was set to 15 minutes. I have only recently taken over JAMF and I think the previous person thought this was the screen saver policy. I set this config policy to 5 seconds and set the screen saver policy under Login Window above to 15 minutes.
After saving and sending, this immediately resolved the issue. The very next reboot, it stopped happening. When I woke the machine up, it gave me my name and then a password box. Accepted my password.
I hope this helps. Are you using 802.1x? Maybe setting the network payload with "Use as a Login Window configuration" would help if that fits your environment. Ive since pushed this policy to at least 5 other macbooks - mix of intel and silicon chips. None of them have shown the issue you're experiencing if youre in this thread.
14.1 Does not solve the issue according to Apple Enterprise. as of 14.1 the only solution is to make the hidden admin account visible and then redeploy the configuration profile that contains the login window settings. So if it is working for you and you haven't made any changes, chances are you weren't experiencing the lock screen issue for the same reason--if you were at all.
3a8082e126