During testing I noticed an intermittent issue with the Apple Push Notification service check on macOS Tahoe 26.5 (Build 25F71) that I wanted to flag.
Issue:
The APNs check is returning an [ERROR] on the second run with exit code 11, with the log output suggesting the log show command output isn't being parsed as expected:
[ERROR] Apple Push Notification service (11): Timestamp Thread Type Activity PID TTL
This appears to be the raw header line from log show output being returned instead of the actual APNs timestamp — suggesting the log query may not be matching any entries on this particular run, and the header is being captured instead of a valid result.
Important to note: the APNs connectivity host checks all passed (courier.push.apple.com, api.push.apple.com — all PASS), so this appears to be a log parsing issue rather than a genuine APNs connectivity failure. The first run on the same machine returned a valid timestamp and passed cleanly.
Environment:
• macOS: Tahoe 26.5 (Build 25F71)
• Mac model: MacBook Pro 14-inch, Nov 2024 (Mac16,8)
• MHC version: 3.2.0
• swiftDialog: 3.0.1.4955
• Operation Mode: Self Service (Jamf Pro)
Log excerpt (Run 1 — pass):
[INFO] Apple Push Notification service: 2026-05-29 21:26:37
Log excerpt (Run 2 — fail):
[ERROR] Apple Push Notification service (11): Timestamp Thread Type Activity PID TTL
Happy to share the full log file if that would be helpful for diagnosis.
Thanks again for the great work on this tool — really appreciate everything you've built and shared with the community.
During testing I noticed an intermittent issue with the Apple Push Notification service check on macOS Tahoe 26.5 (Build 25F71) that I wanted to flag.
Issue:
The APNs check is returning an [ERROR] on the second run with exit code 11, with the log output suggesting the
log showcommand output isn't being parsed as expected:[ERROR] Apple Push Notification service (11): Timestamp Thread Type Activity PID TTL
This appears to be the raw header line from
log showoutput being returned instead of the actual APNs timestamp — suggesting the log query may not be matching any entries on this particular run, and the header is being captured instead of a valid result.Important to note: the APNs connectivity host checks all passed (courier.push.apple.com, api.push.apple.com — all PASS), so this appears to be a log parsing issue rather than a genuine APNs connectivity failure. The first run on the same machine returned a valid timestamp and passed cleanly.
Environment:
• macOS: Tahoe 26.5 (Build 25F71)
• Mac model: MacBook Pro 14-inch, Nov 2024 (Mac16,8)
• MHC version: 3.2.0
• swiftDialog: 3.0.1.4955
• Operation Mode: Self Service (Jamf Pro)
Log excerpt (Run 1 — pass):
[INFO] Apple Push Notification service: 2026-05-29 21:26:37
Log excerpt (Run 2 — fail):
[ERROR] Apple Push Notification service (11): Timestamp Thread Type Activity PID TTL
Happy to share the full log file if that would be helpful for diagnosis.
Thanks again for the great work on this tool — really appreciate everything you've built and shared with the community.