Dear Apple Developer Forum members,
We recently encountered a situation where VoIP Push notifications were not being received under specific conditions. We would greatly appreciate any insights or information regarding the potential cause of this issue and possible countermeasures.
Incident Details:
- Problem: VoIP Push notifications are not being received.
Device Information:
- iPad Air (9th generation)
- OS version: 16.1
Prerequisites for the Issue to Occur:
- Device is operating without a SIM card, using only Wi-Fi connectivity.
- Auto-lock feature in Settings is disabled.
- Low-security Wi-Fi network is being used (specifically, a pocket Wi-Fi device with a low-security label).
Procedure to Reproduce the Issue:
- Leave the app running in the foreground without any user interaction for approximately 5-6 minutes.
- Send a VoIP Push notification to the target device.
- No notification appears on the device.
Investigation Details and Findings:
-
No apsd (Apple Push Notification Service daemon) log output was generated at the time the VoIP Push notification was sent.
- We suspect the apsd process may have been stopped for some reason.
- Is it possible that the apsd process, configured as a wake-on-WAN client, fails to start when the packet is received?
-
Additional information from the macOS Console:
-
Following the log output below, notifications stopped being received:
Default 18:26:12.416462+0900 apsd <private> _disconnectStream for interface: WWAN with reason: 2 Default 18:26:12.416574+0900 apsd <private>: Setting is connected 0 on interface WWAN with reason 2 Default 18:26:12.416681+0900 apsd Connection closed development WWAN Default 18:26:12.416783+0900 apsd <private> canUseProxy: NO isNearby: NO Default 18:26:12.416886+0900 apsd <private> received courierConnectionStatusDidChange from <private>. Default 18:26:12.416986+0900 apsd <private> canUseProxy: NO isNearby: NO Default 18:26:12.417090+0900 apsd <private> canUseProxy: NO isNearby: NO Default 18:26:12.417193+0900 apsd <private> updating network guidance isConnected? YES Default 18:26:12.417296+0900 apsd <private> canUseProxy: NO isNearby: NO Default 18:26:12.417396+0900 apsd <private> canUseProxy: NO isNearby: NO Default 18:26:12.417506+0900 apsd Attempting to roll activity presence salt Default 18:26:12.417606+0900 apsd It has not been long enough since the last roll
-
-
Additional information from the Wi-Fi daemon (wifid) log:
- The following entry was found: "wifid apsd[122] is a wow client."
-
Additionally, we noticed the following recurring log entry:
ERROR: __WiFiLQAMgrIsIntervalChangeAllowed: Too frequent LQM interval change not allowed.
Thank you in advance for any assistance, suggestions, or information you can provide. We are eager to understand the cause of this problem and explore potential remedies.
Best regards,
