Push Center, APNs, Firebase, and device tokens
PlannedPlanned: hosted push remains unavailable until physical-device delivery, authenticated registration, batching, idempotency, invalid-token handling, and tenant isolation are verified.
What this does
Will manage provider credentials, devices, audiences, campaigns, messages, deliveries, and templates.
What you need
Source rebuild, APNs and FCM setup, provider credentials, and physical iOS/Android devices.
What LaunchLayer automates
Planned registration contract, audience resolution, queued batches, provider results, scheduled and event sends, and invalid-token disablement.
What remains external
Apple/Firebase accounts, user permission, client integration, and device verification.
Exact setup steps
Not released; use the generated native push setup plan only.
How to verify it
Permission, initial/refresh registration, logout, individual/segment/scheduled sends, deep links, invalidation, and duplicate prevention must pass.
Common failures
Sandbox/production mix, stale token, denied permission, wrong APNs topic, Firebase mismatch, or duplicate retry.
Security considerations
Tokens and credentials must be encrypted/redacted; sends require rate limits, payload caps, validated deep links, and idempotency.
Related articles
Native features; security and ownership.