Error: The application instance is not registered on the server yet

You might face the following error returned from our API:

"The application instance is not registered on the server yet. The registration will be performed eventually.
Subscribe to the notification `MMRegistrationUpdated` to be notified as the registration succeeded."

This error message tries hard to briefly explain the problem and consequences. But let's bring more details.

At launch time, your app communicates with APNs and receives its device token, which we then forward to our server. Our server creates a push registration based on that token and includes it with any push notifications we send.

Problem

The application instance is not registered on the server yet.

This phrase means that at current moment your app has not yet provided a device token for us. It might happen most likely due to network delays and/or specific firewall settings that your network might potentially have. First of all, try to use another network or even cellular network to eliminate the problem.

Resolution

The registration will be performed eventually.

This phrase means that the actual state of your application missing the device token is temporal and might be resolved eventually by itself, as soon as your app receives the device token from APNs. Once it happened, the Mobile Messaging SDK will immediately forward the device token to our server and a new push registration will be created.

Control

Subscribe to the notification MMRegistrationUpdated to be notified as the registration succeeded.

As mentioned earlier, once the device token is received from APNs, Mobile Messaging SDK will perform the registration on the server and your device would become registered. Key thing here is that this transition will happen "under the hood", silently. If you need to be notified about this event, just subscribe to library event MMRegistrationUpdated. More details on library events here.