Push notifications are essential for keeping employees informed and engaged. When something goes wrong, quick diagnosis is key. This article explains how to use the Push diagnostics and real push tool in the Admin panel to test real push notifications directly on your device and speed up troubleshooting.
The Testing section has been renamed to Local notification.
Overview
The internal Push diagnostics tool allows you to:
- Send real push notifications through the full production pipeline
- Check your device’s push token status
- Verify operating system (OS) permissions
- Review delivery and deep link behaviour in real time
This replaces the previous testing method, which only supported local (simulated) notifications.
When and why it should be used
Use this functionality when:
- A client reports that push notifications are not being received
- You need to validate whether an issue is related to backend delivery or device configuration
- You want to test deep links, priority settings, or custom notification content
- You are troubleshooting notification behaviour directly from a mobile device without external tools
This tool is especially useful for Support, Mobile, and QA teams handling real-time client issues.
How to use
- Open the mobile app on your device
- Access the Admin panel
- Scroll down to Push notification diagnostics
- Review the Device health information, including:
- Push token availability
- OS notification permissions
- Go to the Real push section
- Configure your notification:
- Add a title
- Add a body
- Select a Deep link path
- Set the Priority
- Set the TTL in seconds
- Select a sound (if applicable)
- Tap Send real push
- Check the Inbox to review:
- API response results
- Delivery status
- Error messages (if any)
If you want to test only how a notification looks locally (without backend delivery), use the Local notification section instead.
If the notification was not received on the device, verify that OS notification permissions are enabled, check that a valid push token is generated and review the Log panel for backend errors.
If the deep link does not open the expected screen, confirm the deep link is correctly configured in the backend, review the Log panel to check if the payload contains the correct parameters and validate that the app version supports the tested deep link.
Tips and best practices
- Always check Device health before sending a test push to rule out permission or token issues
- Use clear and unique test titles (e.g., “Test – High Priority – Deep Link”) to easily identify your notification
- When testing deep links, confirm that the expected screen opens correctly after tapping the notification
- If testing priority levels, compare behaviour in both foreground and background app states
- Ensure your device has a stable internet connection before running tests
FAQ
-
What is the difference between Real push and Local notification?
Real push sends a notification through the full production backend pipeline. Local notification simulates a notification directly on the device without contacting the backend.
-
Does this tool send notifications to real employees?
No. It sends notifications only to the device from which the test is triggered.
-
Can this tool be used in production environments?
Yes, it uses the production pipeline, but it is designed for controlled internal testing on your own device.