Hey Team, We're experiencing an issue where push notifications are failing to deliver to certain devices in the production environment. However, they are working fine in the development build on specific devices. Interestingly, the notifications are working fine for a few devices in the same production environment. In the affected devices we have attempted the following things to resolve the issue Verify the device token (& send the notification through apple push notification console) reinstall the application reboot the device Below are the device details Model - Macbook Pro 15-inch, 2018 processor - 2.9 GHz 6-Core Intel Core i9 OS Version - macOS Sonoma 14.2.1 I have attached the APSD process console log for the affected device. In which we are getting following error. apsd Peer connection [pid=472] lacks APSConnectionInitiateEntitlement APSD_ConsoleLog.txt Thank you all in advance for any information regarding this issue and we will provide any additional information if needed.

Dear Team, I'm encountering challenges in securely storing key-value pairs at the system level keychain on macOS, with the requirement for universal accessibility of that values across all the users in mac. Is it feasible to fulfill this requirement using Keychain? Are there any alternative secure methods for achieving this? Your assistance in finding a solution would be greatly appreciated. Thank you in advance!

Hi Team, I am testing federated authentication of Google Workspace with Apple Business Manager (ABM). After successfully configuring the Google Workspace domain in the ABM admin account and syncing it, we attempted to enroll a device using automated device enrollment and login with the Google Workspace account as the managed Apple ID. However, during enrollment, the system asked to create a new user, even though the username was replicated from the Google account, and prompted to enter a new password. Could someone please explain why this is happening? and aiming to enable a seamless login without user creation or password generation.

Hi Team, We are trying to erase a mac using following EraseDevice Command with PIN. But We are getting different behaviour in devices. Device Model : MacBook Pro with T2 Security chip macOS : 11.7.2 Result : Device gets wiped but it does not ask for the six digit PIN while installing OS. Device Model : MacBook Air with No Security chip macOS : 12.6.1 Result : Device does not get wiped. It reboots and asks for the six digit PIN before starting. Could you please let us know what is the exact behaviour of Erase Command in different macOS?

Our device is enrolled in MDM & screen locked with a passcode. We don't know the passcode. The device has been rebooted and is at the passcode screen - at this point, we see that it does not have a WiFi connection, so are not able to clear the passcode using a command from our MDM. We are not able to erase the device because there is some sensitive data in there that we would like to recover. Is there any way a device can be made to connect to a network when it is waiting at the passcode entry screen?