Server errors

The MobileMessaging SDK wraps server error information into NSError. The following example demonstrates how an error code and a message attributes may be retrieved from the error object:

if let user = MobileMessaging.getUser() {
    user.emails = ["email@invalid"]
    MobileMessaging.saveUser(user, completion: { error in
        print(error.mm_code) // prints "EMAIL_INVALID"
        print(error.mm_message) // prints "Invalid email: email@invalid"
    })
}

New user/installation data APIs, starting from Mobile Messaging 5.0

Error code	Error message	Explanations
EMAIL_INVALID	"Invalid email: {email}"	Emails should have valid format (https://tools.ietf.org/html/rfc2822)
PHONE_INVALID	Invalid phone number: {number} ({details})	Phone number should have valid format (https://en.wikipedia.org/wiki/E.164)
USER_IDENTITY_INVALID	MMUserIdentity does not have any identity field set	MMUserIdentity must have at least one field (phone/email/externalUserId) set, SDK takes care of it by providing failable initializer for you.
USER_MERGE_INTERRUPTED	User update violates unique key constraint	This error may happen when you try to saveUser with unique attribute that refers to another Person record on the server
PERSONALIZATION_IMPOSSIBLE	Installation is not depersonalized. Personalization is prohibited	This error happens when you try to re-personalize current installation using MMUserIdentity that is currently identifies another person. In such case you need to depersonalize first. To make both operations (depersonalize and personalize again) at once use MobileMessaging.personalize(forceDepersonalize: true, ...) API.
AMBIGUOUS_PERSONALIZE_CANDIDATES	Several users satisfy supplied user identity	This error happpens when you try to personalize current installation with a MMUserIdentity matching several existing persons. This operation cannot be done by design. We recommend either to use only one field for personalization as a best practice, or to pay very close attention to what you personalize your installations with - keep it consistent and unique.
USER_DATA_RESTRICTED	User update access is restricted	This error happens when you use saveUser whereas on Infobip Portal you set "Restrict saving sensitive data from SDK"
REQUEST_FORMAT_INVALID	{Field name} should be {supported type}	Predefined user/installation data attribute has wrong type. SDK takes care of types for predefined user/installation attributes for you.
APP_CODE_MISSING	Application code not provided	Application code is a mandatory parameter for all server requests
NO_REGISTRATION	Registration does not exist	In most cases the error means that the current push registration was expired and no longer valid. We detect that the APNS device token becomes invalid (due to wrong app settings regarding APNS environment or app uninstallation) and expire the push registration accordingly
ACCESS_TOKEN_MISSING	Access token not provided	This error means that the server API requires an access token to authenticate actual application user. Might happen in case of fetching Inbox messages (learn more about token based authorization).
UNAUTHORIZED	Invalid login details	The error means that the authorization data provided by the SDK is invalid. It means that an Application Code that you use to start MM SDK might be wrong or deleted on Infobip Portal; or an Access Token that you generated and provided has invalid payload, signed with a wrong secret key or has been expired (learn more about token based authorization).

Other APIs (seen, messages sync, message sending, geo event reporting)

Error code	Error message	Explanations
0	Something went wrong [10000]	This is really unknown, and most likely we are already working to fix things
1	Invalid Application Id [10001]	The application code you provided to the SDK doesn't exists
2, 4, 7, 8, 10, 11, 12, 13	Internal service error [xxxxx]	There is nothing you can do with these errors, except retrying later. Most likely we're already fixing stuff, but you are always welcome to ask for support at [email protected]