Who should use this
- Mobile engineers validating push payloads before release
- Support teams replaying incident payloads
- DevOps staff testing notification workflows for staging environments
Push Notification test
Push Notification Testing Tool / Gateway Demo is designed to enable developers to test sending push notifications to Android and iOS devices. It appears as a simple interface where you can configure and send messages using both Firebase Cloud Messaging (FCM) and Apple Push Notification Service (APNs).
Push Notification
53 views
December 31, 2025
How it works
Upload Firebase service accounts or APNs certificates so the demo can authenticate directly without storing secrets.
Craft payloads, choose device tokens, and send pushes while watching live responses and error logs.
Step-by-step usage
- Upload the Firebase or APNs credentials you trust.
- Compose a payload with headers, body, and target platform.
- Send and verify the delivery log before updating production rules.
Limitations / safety notes
Uploads stay in memory for your session; we never persist your certificates or service accounts beyond the current browser tab.
Real-world use cases
Release-day notification checks
Validate payload content, priority, and token targeting in staging before enabling production campaigns.
Post-incident replay
Replay failed push payloads from incident timelines to confirm whether failures are auth, token, or payload-structure related.
Cross-platform parity
Verify that Android (FCM) and iOS (APNs) receive equivalent notification content and metadata when campaigns go live.
Troubleshooting guide
401/403 push response
Likely cause: Expired credentials or missing role permissions
Recommended action: Rotate credentials and verify service account / APNs key scopes.
Delivered to Android but not iOS
Likely cause: APNs headers or topic configuration mismatch
Recommended action: Check APNs topic, push type, and certificate environment alignment.
Intermittent token failures
Likely cause: Stale device tokens after app reinstall or logout
Recommended action: Refresh tokens from client devices and prune invalid targets.
Implementation checklist
- Test payloads in staging before campaign launch.
- Log response IDs and error classes for incident replay.
- Separate credential sets for dev, staging, and production.
- Document rollback path for failed notification batches.
Tool-specific FAQ
Can I push to both Android and iOS from a single request?
Yes-the tool splits the payload and uses the right protocol (FCM for Android, APNs for iOS) while sharing your custom JSON body.
Is there rate limiting?
The demo enforces a soft limit to protect your credentials; if you hit it, retry after a few seconds or refresh the tool.
Related guides
Ready to use this app?
Click the button to open it in your workspace.