Where can we add test devices to the panel?
You can add your test devices through Components > Integrations > Mobile App Components > Test Devices.
How can we add a test device to the panel?
You can follow one of the three methods:
Add by identifier
Once you determine your device’s UDID, you can add it to test devices. Go to Components > Integrations > Mobile App Components > Test Devices and click the Create button. The identifier will usually be a UDID. After adding in the value of your UDID, click the Create button. If you have users in our database, you can also choose a different type of identifier, like email, name, last name, etc., to add the user and their device to the test devices.
Send an email with a dynamic link
Enter your email address and click the Send Email button. You will receive an email from mobile-info@useinsider.com. Open it on your mobile device and follow the related steps to add your device as a test device.
Scan a QR code
Select the QR Code option, and a QR code will be generated on your screen.
Scan this code using your mobile device to register it as a test device.
If the test device is not listed after scanning the QR code, the respective device might have already been added as a test device. To understand if this device has been previously added as a test device, wait for at least 30 seconds after scanning the QR code and reloading the page. If the device is still not visible on the list, go to Components > Integrations > Mobile App Components > Test Devices to remove any test devices with the same device model and try again.
Do we need extra integration for adding a test device via a dynamic link?
For Android, there is no need for extra integration. For iOS, there is an extra integration.
Where canwe see the test devices that are added to the panel?
You can see them via Components > Integrations > Mobile App Components > Test Devices.
We see that the test push is delivered to iOS devices even though we segmented only Android users while creating the campaign. Is there an error regarding the test push?
No, the messages are sent to all the devices in the test devices list. Thus, the behavior is expected.
What is the reason of Bad Device Token Error?
The application and the app environment do not match. One is in development, and the other is in the production environment. iOS pushes are sent from two environments: production and development. The pushes sent from the development environment are delivered to the development version of the application, and the pushes sent from the production environment are delivered to the production version of the application.
What is the reason of Mismatch Sender ID Error?
To send notifications to Android devices, the sender ID and the Firebase API Key must match. In the cases where these two values are different, we cannot send pushes to Android users.
What is the reason of Unregistered Error?
The user uninstalled the app and is no longer reachable on the iOS platform. To send a test push, the user should delete the application, install it, and add the device as a test device again.
What is the reason of Not Registered Error?
The user uninstalled the app and is no longer reachable on the Android platform. This error is generally seen on Android SDK versions over 8.0 since the UDID changes after the user deletes and installs the application again. You need to add the device as a test device again.
What is the reason of No Device Token Error?
If a device doesn't give push notification permission, then it will receive this error. The push notification permission should be allowed.
What is the reason of Device Token Not For Topic Error?
It means the push notification certificate topic and the application package name do not match.