The cross-platform audit of #10416 found that APNs has delivery-attempt records and queue tracing, while FCM primarily records the delivered aggregate and uses generic delivery results. This makes equivalent failures harder to investigate on Android.
Follow-up scope:
- Define shared delivery outcomes for queued, sent, skipped, invalid-token, and retryable failures while preserving existing wire compatibility.
- Give FCM queue processing the same trace context and safe device/environment/job annotations as APNs.
- Exercise equivalent retry, preference, freshness, and token-rotation cases through both adapters.
The current Android review fixes preserve immediate transport causes. This issue tracks the broader diagnostics work separately from shipping the Android adapter.
The cross-platform audit of #10416 found that APNs has delivery-attempt records and queue tracing, while FCM primarily records the delivered aggregate and uses generic delivery results. This makes equivalent failures harder to investigate on Android.
Follow-up scope:
The current Android review fixes preserve immediate transport causes. This issue tracks the broader diagnostics work separately from shipping the Android adapter.