In some scenarios it can happen that the token field is empty.
In order to receive a push, it is essential for a profile to have a token. If the field is empty the notification will not be received.
Indeed, the token is an identifier which stock data numbers for the notifications. For instance, equivalent to the e-mail, he is the key that allows the messages broadcast to mobile users.
You will find below the cases where the token field can be blank and what to check in order to resolve this behavior :
1. Is the method "registerForUserNotificationsWithOptions" properly integrated ?
It can happen that the method to recover the token is not correctly integrated.
In order to check this point you will find below the technical documentation.
2. Is the token sent at every opening of the app?
In some cases it can happen that even if the method above is integrated, the token is not sent at each opening to our SDK.
In order to check this issue you can verify the point with your deviceID via our Test Tool.
If this one is not present at each opening, please check again the integration of the method with our technical documentation.
During your tests we also recommend checking the quality of your connection.
Indeed, it can affect the sending of data.
If the point persists, we invite you to reach out to our technical support.