Code

Internal SDK Error. No information available

Internal server error. No information available.

The connection to the Parse servers failed.

Object doesn’t exist, or has an incorrect password.

You tried to find values matching a datatype that doesn’t support exact database matching, like an array or a dictionary.

Missing or invalid classname. Classnames are case-sensitive. They must start with a letter, and a-zA-Z0-9_ are the only valid characters.

Missing object id.

Invalid key name. Keys are case-sensitive. They must start with a letter, and a-zA-Z0-9_ are the only valid characters.

Malformed pointer. Pointers must be arrays of a classname and an object id.

Malformed json object. A json dictionary is expected.

Tried to access a feature only available internally.

Field set to incorrect type.

Invalid channel name. A channel name is either an empty string (the broadcast channel) or contains only a-zA-Z0-9_ characters and starts with a letter.

Invalid device token.

Push is misconfigured. See details to find out how.

The object is too large.

That operation isn’t allowed for clients.

The results were not found in the cache.

Keys in NSDictionary values may not include $ or ..

Invalid file name. A file name can contain only a-zA-Z0-9_. characters and should be between 1 and 36 characters.

Invalid ACL. An ACL with an invalid format was saved. This should not happen if you use ACL.

The request timed out on the server. Typically this indicates the request is too expensive.

The email address was invalid.

Missing content type.

Missing content length.

Invalid content length.

File was too large.

Failure saving a file.

A unique field was given a value that is already taken.

Role’s name is invalid.

Exceeded an application quota. Upgrade to resolve.

Cloud Code script had an error.

Cloud Code validation failed.

Fail to convert data to image.

Unsaved file failure.

An invalid push time.

Fail to delete file.

Fail to delete an unnamed file.

Application has exceeded its request limit.

The request was a duplicate and has been discarded due to idempotency rules.

Invalid event name.

Invalid value.

Username is missing or empty.

Password is missing or empty.

Username has already been taken.

Email has already been taken.

The email is missing, and must be specified.

A user with the specified email was not found.

The user cannot be altered by a client without the session.

Users can only be created through sign up.

An existing account already linked to another user.

The current session token is invalid.

Error enabling or verifying MFA.

A valid MFA token must be provided.

Linked id missing from request.

Invalid linked session.

Error code indicating that a service being linked (e.g. Facebook or Twitter) is unsupported.

Error code indicating an invalid operation occured on schema

Error code indicating that there were multiple errors. Aggregate errors have an “errors” property, which is an array of error objects with more detail about each error that occurred.

Error code indicating the client was unable to read an input file.

Error code indicating a real error code is unavailable because we had to use an XDomainRequest object to allow CORS requests in Internet Explorer, which strips the body from HTTP responses that have a non-2XX status code.

Error code indicating any other custom error sent from the Parse Server.