@DTS Engineer Thank you for your response. Here is some additional explanation regarding our situation: • When we sent a normal alert push from the CloudKit Push Notification Console, we did not include "content-available" and set the priority to 10. • When we sent silent pushes, we set "content-available" to 1 and the priority was 5. • For LPSE (apns-type “location”) pushes, the ones sent from our own server included "content-available" and were sent with priority 10. However, the LPSE pushes sent from the CloudKit Push Notification Console did not include "content-available" (using the Console’s default settings) and were sent with priority 10. After instituting a cool-down period of several days with no notifications sent, we resumed sending LPSE pushes via the CloudKit Console (development environment) and observed divergent behavior among devices: Device A: – The LPSE push continues to be discarded.     2025/03/23 21:55:22.000 JST – Received by APNS Server 2025/03/23 21:55:22.034 JST – Discarded because the user disabled notifications for the app When we sent a normal alert push (priority 10) from the Console, it was "Successfully delivered to the target device." (Note that we did not send any notifications from our own server in this case.) Device B: – The LPSE push was initially received, but later it was discarded. 2025/03/23 20:48:24.053 JST – Received by APNS Server 2025/03/23 20:48:24.247 JST – Successfully delivered to the target device 2025/03/23 21:55:41.414 JST – Received by APNS Server 2025/03/23 21:55:41.446 JST – Discarded because the user disabled notifications for the app Additionally, in the case where the initial LPSE push appears to have been successfully delivered (Device B), we did not see any sign that the extension’s didReceiveLocationPushPayload method was triggered (our NSLog statements do not appear in Console.app), and we did not observe any location data being saved to our server. Since we have not changed the settings that previously allowed the extension to be launched, we believe there is no issue with our implementation. We appreciate your insights into this matter and would welcome any further recommendations regarding the LPSE behavior.

Additional information: When I sent an LPSE from the CloudKit Notification Console in the development environment, I confirmed the following in the delivery log. received by APNS Server discarded because the user disabled notifications for the app (The application is available on the device but the user disabled notifications for it) However, when I sent a normal notification with "apns-type" of alert instead of location, the device received it successfully. By the way, we allowed a certain amount of cooldown time for this test device, leaving it without receiving any new notifications for a full day after it was no longer able to receive LPSE, but the situation did not improve.