Facebook there was an error with your registration please try registering again

Fix There Was An Error With Your Registration. Please Try Registering Again Problem Solved Facebook

In this blog, I am going to tell you How To Fix Facebook Registration Error There Was An Error With Your Registration. Please Try Registering Again Problem Solved in Windows. If you want to know then please read the blog carefully.

• Click on the Search icon .

• Then Again Go on the Search icon .

• Then go to Network And Internet .

• Then go to Network And Sharing Center.

• Then go to Change Adapter Settings .

• Select Your Network And Right Click on it and Go to Properties .

• Then click on Internet Protocol Version 4(TCP/IPv4)

• Then click on Properties .

• Then click on Use the following DNS server addresses:

• Preferred DNS server: 8. 8. 8. 8

• Alternate DNS server: 8. 8. 4. 4

• Then click on OK .

• Then Restart Your Device.

• Doing all these, your problem of How To Fix Facebook Registration Error There Was An Error With Your Registration. Please Try Registering Again Problem Solved in Windows in Windows 11,10,8,7 will definitely be solved .

Thanks for Visiting Our Website .

Techsore

You may like these posts

If you have any doubt, then comment to me, I will tell you the solution to that doubt.
Please do not enter any spam comments.

Источник

Как разблокировать аккаунт после 5 неудачных попыток входа

Как разблокировать аккаунт после 5 неудачных попыток входа

Наверное, каждый сталкивался с ошибкой при попытке авторизации с не валидными данными, которая по-английски звучит так

Sorry, there have been more than 5 failed login attempts for this account. It is temporarily blocked. Try again later or request a new password.

Аккаунт временно заблокирован по причине более чем 5 неудачных попыток входа. Попробуйте войти позже, или запросите новый пароль.

Это простая самооборона Друпала, которая активируется после 5 (по умолчанию) попыток входа. Таким образом, система не позволяет злоумышленникам забрутофорсить (англ. brute force. Cм. Полный перебор) сайт. Работает она достаточно просто: во время каждой авторизации, Друпал сохраняет ip-адрес пользователя, запоминая при этом, точную дату события и дату окончания «срока годности» попытки.

Вот некоторые нюансы:

• По умолчанию «срок годности» составляет 1 земной час.
• Количество возможных, неудачных попыток входа — 5.
• Эти значения могут быть изменены.
• Вместо ip-адреса может быть сохранено имя хоста.
• Данные, у которых истек «срок годности» очищаются только по крону.
• Вы можете войти в систему, в любом случае если пройдете процедуру «Сброса пароля»!

Вот еще один интересный факт:

Вы можете имя пользователя указать верно, но при этом 5 раз ошибиться с паролем. В таком случае, попытки авторизации будут запрещены на 6 часов. При этом, через 60 минут можно будет повторить попытку входа, но с другого ip-адреса.

Что касается простых смертных — мы разобрались. Администраторы, же или программисты могут сталкиваться с этой проблемой чаще, т.к. им хлеб в рот не клади, дай только что-нибудь сломать. К счастью, для тех у кого есть доступ к Драшу или напрямую к базе могут обойтись без сброса пароля или часового ожидания. Нужно просто почистить таблицу flood
. Вот восемь способов это сделать.

Проблемы, ошибки, неточности в тексте пишите в комментах.

Источник

Name already in use

all-exit-error-codes / api / facebook / facebook.md

• Go to file T
• Go to line L
• Copy path
• Copy permalink

Copy raw contents

Copy raw contents

Facebook API Error Codes for Developers

This list is heavily based on

Should this stay in table format? Seems quite unbearable to keep it handled in tables. Also I didn’t take into account «Generated by methods»

General Errors

• 0 — API_EC_SUCCESS: Success
• 1 — API_EC_UNKNOWN: An unknown error occurred
• 2 — API_EC_SERVICE: Service temporarily unavailable
• 3 — API_EC_METHOD: Unknown method
• 4 — API_EC_TOO_MANY_CALLS: Application request limit reached
• 5 — API_EC_BAD_IP: Unauthorized source IP address
• 6 — API_EC_HOST_API: This method must run on api.facebook.com
• 7 — API_EC_HOST_UP: This method must run on api-video.facebook.com
• 8 — API_EC_SECURE: This method requires an HTTPS connection
• 9 — API_EC_RATE: User is performing too many actions
• 10 — API_EC_PERMISSION_DENIED: Application does not have permission for this action
• 10 — User cannot edit action
• 10 — User cannot delete action
• 10 — Not a Messenger client
• 10 — The app updating this status card must be the same one that created the corresponding page’s CTA.
• 11 — API_EC_DEPRECATED: This method is deprecated
• 12 — API_EC_VERSION: This API version is deprecated
• 13 — API_EC_INTERNAL_FQL_ERROR: The underlying FQL query made by this API call has encountered an error. Please check that your parameters are correct.
• 14 — API_EC_HOST_PUP: This method must run on api-photo.facebook.com
• 15 — API_EC_SESSION_SECRET_NOT_ALLOWED: This method call must be signed with the application secret (You are probably calling a secure method using a session secret)
• 16 — API_EC_HOST_READONLY: This method cannot be run on this host, which only supports read-only calls
• 17 — API_EC_USER_TOO_MANY_CALLS: User request limit reached
• 18 — API_EC_REQUEST_RESOURCES_EXCEEDED: This API call could not be completed due to resource limits
• 27 — This app does not have permission to manage this Facebook at Work account.

Parameter Errors

• 100 — API_EC_PARAM: Invalid parameter
• 100 — No permission to publish the video
• 100 — Cannot post to User Likes with Page Access Token
• 100 — Parameters do not match any fields that can be updated
• 100 — Object does not support message editing
• 100 — Please enter a valid email address
• 100 — Comment not found
• 100 — inst_type must be one of the following values: CreditCard, ApplePayCard
• 100 — Unsupported post request. Object with ID ‘me’ does not exist, cannot be loaded due to missing permissions, or does not support this operation. Please read the Graph API documentation at https://developers.facebook.com/docs/graph-api
• 100 — Must be a valid ISO 4217 currency code
• 101 — API_EC_PARAM_API_KEY: Invalid API key
• 102 — API_EC_PARAM_SESSION_KEY: Session key invalid or no longer valid
• 103 — API_EC_PARAM_CALL_ID: Call_id must be greater than previous
• 104 — API_EC_PARAM_SIGNATURE: Incorrect signature
• 105 — API_EC_PARAM_TOO_MANY: The number of parameters exceeded the maximum for this operation
• 110 — API_EC_PARAM_USER_ID: Invalid user id
• 111 — API_EC_PARAM_USER_FIELD: Invalid user info field
• 112 — API_EC_PARAM_SOCIAL_FIELD: Invalid user field
• 113 — API_EC_PARAM_EMAIL: Invalid email
• 114 — API_EC_PARAM_USER_ID_LIST: Invalid user ID list
• 114 — An id must be a valid ID string (e.g., «123»)
• 115 — API_EC_PARAM_FIELD_LIST: Invalid field list
• 120 — API_EC_PARAM_ALBUM_ID: Invalid album id
• 121 — API_EC_PARAM_PHOTO_ID: Invalid photo id
• 130 — API_EC_PARAM_FEED_PRIORITY: Invalid feed publication priority
• 140 — API_EC_PARAM_CATEGORY: Invalid category
• 141 — API_EC_PARAM_SUBCATEGORY: Invalid subcategory
• 142 — API_EC_PARAM_TITLE: Invalid title
• 143 — API_EC_PARAM_DESCRIPTION: Invalid description
• 145 — API calls from the server require an appsecret_proof argument
• 144 — API_EC_PARAM_BAD_JSON: Malformed JSON string
• 150 — API_EC_PARAM_BAD_EID: Invalid eid
• 151 — API_EC_PARAM_UNKNOWN_CITY: Unknown city
• 152 — API_EC_PARAM_BAD_PAGE_TYPE: Invalid page type
• 170 — API_EC_PARAM_BAD_LOCALE: Invalid locale
• 180 — API_EC_PARAM_BLOCKED_NOTIFICATION: This notification was not delieved
• 190 — API_EC_PARAM_ACCESS_TOKEN: Invalid OAuth 2.0 Access Token
• 190 — The access token does not match the user claiming the offer
• 190 — The access token does not match the user resending the offer
• 193 — The time specified is too far back in the past. Please do a full refresh of the friends using the friend FQL table

User Permission Errors

• 200 — API_EC_PERMISSION: Permissions error
• 200 — User does not have permission to post to target
• 200 — Video is either deleted or you do not have permission to view it
• 200 — This post wasn’t created by the application
• 200 — Posts where the actor is a page cannot also include a target_id other than EVENT or GROUP»
• 200 — Subject does not have permission to create live video on this page
• 200 — Subject does not have permission to create live video on this user
• 210 — API_EC_PERMISSION_USER: User not visible
• 211 — API_EC_PERMISSION_NO_DEVELOPERS: Application has no developers.
• 212 — API_EC_PERMISSION_OFFLINE_ACCESS: Renewing a session offline requires the extended permission offline_access
• 220 — API_EC_PERMISSION_ALBUM: Album or albums not visible
• 220 — User cannot delete this album.
• 221 — API_EC_PERMISSION_PHOTO: Photo not visible
• 230 — API_EC_PERMISSION_MESSAGE: Permissions disallow message to user
• 240 — API_EC_PERMISSION_MARKUP_OTHER_USER: Desktop applications cannot set FBML for other users
• 240 — This user isn’t allowed to upload photos to this object’s wall
• 250 — API_EC_PERMISSION_STATUS_UPDATE: Updating status requires the extended permission status_update.
• 260 — API_EC_PERMISSION_PHOTO_UPLOAD: Modifying existing photos requires the extended permission photo_upload
• 261 — API_EC_PERMISSION_VIDEO_UPLOAD: Modifying existing photos requires the extended permission photo_upload
• 270 — API_EC_PERMISSION_SMS: Permissions disallow sms to user.
• 270 — Development access is not allowed to access business API post:Business/adaccount.
• 273 — This Ads API call requires the user to be admin of the ad account. User not admin on ad account
• 275 — Reading advertisements requires an access token with the extended permission ads_read
• 280 — API_EC_PERMISSION_CREATE_LISTING: Creating and modifying listings requires the extended permission create_listing
• 281 — API_EC_PERMISSION_CREATE_NOTE: Managing notes requires the extended permission create_note.
• 282 — API_EC_PERMISSION_SHARE_ITEM: Managing shared items requires the extended permission share_item.
• 290 — API_EC_PERMISSION_EVENT: Creating and modifying events requires the extended permission create_event
• 291 — API_EC_PERMISSION_LARGE_FBML_TEMPLATE: FBML Template isn’t owned by your application.
• 292 — API_EC_PERMISSION_LIVEMESSAGE: An application is only allowed to send LiveMessages to users who have accepted the TOS for that application.
• 293 — API_EC_PERMISSION_XMPP_LOGIN: Logging in to chat requires the extended permission xmpp_login
• 294 — API_EC_PERMISSION_ADS_MANAGEMENT: Managing advertisements requires the extended permission ads_management, and a participating API key
• 296 — API_EC_PERMISSION_CREATE_EVENT: Managing events requires the extended permission create_event
• 298 — API_EC_PERMISSION_READ_MAILBOX: Reading mailbox messages requires the extended permission read_mailbox
• 299 — API_EC_PERMISSION_RSVP_EVENT: RSVPing to events requires the extended permission create_rsvp

Data Editing Errors

• 300 — API_EC_EDIT: Edit failure
• 310 — API_EC_EDIT_USER_DATA: User data edit failure
• 320 — API_EC_EDIT_PHOTO: Photo edit failure
• 320 — This photo is not wide enough to use as a Timeline Cover, the minimum width is 399 pixels
• 321 — API_EC_EDIT_ALBUM_SIZE: Album is full
• 322 — API_EC_EDIT_PHOTO_TAG_SUBJECT: Invalid photo tag subject
• 323 — API_EC_EDIT_PHOTO_TAG_PHOTO: Cannot tag photo already visible on Facebook
• 324 — API_EC_EDIT_PHOTO_FILE: Missing or invalid image file
• 325 — API_EC_EDIT_PHOTO_PENDING_LIMIT: Too many unapproved photos pending
• 326 — API_EC_EDIT_PHOTO_TAG_LIMIT: Too many photo tags pending
• 327 — API_EC_EDIT_ALBUM_REORDER_PHOTO_NOT_IN_ALBUM: Input array contains a photo not in the album
• 328 — API_EC_EDIT_ALBUM_REORDER_TOO_FEW_PHOTOS: Input array has too few photos
• 329 — API_EC_MALFORMED_MARKUP: Template data must be a JSON-encoded dictionary, of the form
• 330 — API_EC_EDIT_MARKUP: Failed to set markup
• 340 — API_EC_EDIT_FEED_TOO_MANY_USER_CALLS: Feed publication request limit reached
• 341 — API_EC_EDIT_FEED_TOO_MANY_USER_ACTION_CALLS: Feed action request limit reached
• 342 — API_EC_EDIT_FEED_TITLE_LINK: Feed story title can have at most one href anchor
• 343 — API_EC_EDIT_FEED_TITLE_LENGTH: Feed story title is too long
• 344 — API_EC_EDIT_FEED_TITLE_NAME: Feed story title can have at most one fb:userlink and must be of the user whose action is being reported
• 345 — API_EC_EDIT_FEED_TITLE_BLANK: Feed story title rendered as blank
• 346 — API_EC_EDIT_FEED_BODY_LENGTH: Feed story body is too long
• 347 — API_EC_EDIT_FEED_PHOTO_SRC: Feed story photo could not be accessed or proxied
• 348 — API_EC_EDIT_FEED_PHOTO_LINK: Feed story photo link invalid
• 350 — API_EC_EDIT_VIDEO_SIZE: Video file is too large
• 351 — API_EC_EDIT_VIDEO_INVALID_FILE: Video file was corrupt or invalid
• 352 — API_EC_EDIT_VIDEO_INVALID_TYPE: Video file format is not supported
• 353 — API_EC_EDIT_VIDEO_FILE: Missing video file
• 354 — API_EC_EDIT_VIDEO_NOT_TAGGED: User is not tagged in this video
• 355 — API_EC_EDIT_VIDEO_ALREADY_TAGGED: User is already tagged in this video
• 360 — API_EC_EDIT_FEED_TITLE_ARRAY: Feed story title_data argument was not a valid JSON-encoded array
• 361 — API_EC_EDIT_FEED_TITLE_PARAMS: Feed story title template either missing required parameters, or did not have all parameters defined in title_data array
• 362 — API_EC_EDIT_FEED_BODY_ARRAY: Feed story body_data argument was not a valid JSON-encoded array
• 363 — API_EC_EDIT_FEED_BODY_PARAMS: Feed story body template either missing required parameters, or did not have all parameters defined in body_data array
• 364 — API_EC_EDIT_FEED_PHOTO: Feed story photos could not be retrieved, or bad image links were provided
• 365 — API_EC_EDIT_FEED_TEMPLATE: The template for this story does not match any templates registered for this application
• 366 — API_EC_EDIT_FEED_TARGET: One or more of the target ids for this story are invalid. They must all be ids of friends of the acting user
• 367 — API_EC_EDIT_FEED_MARKUP: The template data provided doesn’t cover the entire token set needed to publish the story
• 368 — The action attempted has been deemed abusive or is otherwise disallowed
• 370 — API_EC_USERS_CREATE_INVALID_EMAIL: The email address you provided is not a valid email address
• 371 — API_EC_USERS_CREATE_EXISTING_EMAIL: The email address you provided belongs to an existing account
• 372 — API_EC_USERS_CREATE_BIRTHDAY: The birthday provided is not valid
• 373 — API_EC_USERS_CREATE_PASSWORD: The password provided is too short or weak
• 374 — API_EC_USERS_REGISTER_INVALID_CREDENTIAL: The login credential you provided is invalid.
• 375 — API_EC_USERS_REGISTER_CONF_FAILURE: Failed to send confirmation message to the specified login credential.
• 376 — API_EC_USERS_REGISTER_EXISTING: The login credential you provided belongs to an existing account
• 377 — API_EC_USERS_REGISTER_DEFAULT_ERROR: Sorry, we were unable to process your registration.
• 378 — API_EC_USERS_REGISTER_PASSWORD_BLANK: Your password cannot be blank. Please try another.
• 379 — API_EC_USERS_REGISTER_PASSWORD_INVALID_CHARS: Your password contains invalid characters. Please try another.
• 380 — API_EC_USERS_REGISTER_PASSWORD_SHORT: Your password must be at least 6 characters long. Please try another.
• 381 — API_EC_USERS_REGISTER_PASSWORD_WEAK: Your password should be more secure. Please try another.
• 382 — API_EC_USERS_REGISTER_USERNAME_ERROR: Our automated system will not approve this name.
• 383 — API_EC_USERS_REGISTER_MISSING_INPUT: You must fill in all of the fields.
• 384 — API_EC_USERS_REGISTER_INCOMPLETE_BDAY: You must indicate your full birthday to register.
• 385 — API_EC_USERS_REGISTER_INVALID_EMAIL: Please enter a valid email address.
• 386 — API_EC_USERS_REGISTER_EMAIL_DISABLED: The email address you entered has been disabled. Please contact disabled@facebook.com with any questions.
• 387 — API_EC_USERS_REGISTER_ADD_USER_FAILED: There was an error with your registration. Please try registering again.
• 388 — API_EC_USERS_REGISTER_NO_GENDER: Please select either Male or Female.

Authentication Errors

400 — API_EC_AUTH_EMAIL: Invalid email address

401 — API_EC_AUTH_LOGIN: Invalid username or password

402 — API_EC_AUTH_SIG: Invalid application auth sig

403 — API_EC_AUTH_TIME: Invalid timestamp for authentication

412 — User has not installed the application

Session Errors

• 450 — API_EC_SESSION_TIMED_OUT: Session key specified has passed its expiration time
• 451 — API_EC_SESSION_METHOD: Session key specified cannot be used to call this method
• 452 — API_EC_SESSION_INVALID: Session key invalid. This could be because the session key has an incorrect format, or because the user has revoked this session
• 453 — API_EC_SESSION_REQUIRED: A session key is required for calling this method
• 454 — API_EC_SESSION_REQUIRED_FOR_SECRET: A session key must be specified when request is signed with a session secret
• 455 — API_EC_SESSION_CANNOT_USE_SESSION_SECRET: A session secret is not permitted to be used with this type of session key
• 456 — The session is malformed
• 457 — The session has an invalid origin
• 458 — User USER_ID has not authorized application APP_ID
• 459 — The user has been checkpointed. The error_data will contain the URL the user needs to go to to clear the checkpoint
• 460 — Session does not match current stored session. This may be because the user changed the password since the time the session was created or Facebook has changed the session for security reasons
• 461 — Session is invalid. This could be because the application was uninstalled after the session was created
• 462 — The session has a stale version
• 464 — The session user is not confirmed
• 463 — Session has expired at unix time SOME_TIME. The current unix time is SOME_TIME
• 465 — The session user is invalid
• 466 — The session was invalidated explicitly using an API call
• 467 — The session is invalid because the user logged out
• 468 — The session is invalid, because the user has not used the app for a long time
• 478 — The images you tried to upload are too many

Application Messaging Errors

500 — API_EC_MESG_BANNED: Message contains banned content

501 — API_EC_MESG_NO_BODY: Missing message body

502 — API_EC_MESG_TOO_LONG: Message is too long

503 — API_EC_MESG_RATE: User has sent too many messages

504 — API_EC_MESG_INVALID_THREAD: Invalid reply thread id

505 — API_EC_MESG_INVALID_RECIP: Invalid message recipient

506 — Duplicate status message

509 — Invalid attachment extension

510 — API_EC_POKE_INVALID_RECIP: Invalid poke recipient

511 — API_EC_POKE_OUTSTANDING: There is a poke already outstanding

512 — API_EC_POKE_RATE: User is poking too fast

513 — API_EC_POKE_USER_BLOCKED: User cannot poke via API

521 — You can’t add yourself as a friend

522 — You are already friends with this user

528 — This user already has too many friend requests

546 — The type of file you’re trying to attach isn’t allowed. Please try again with a different format.

FQL Errors

• 600 — FQL_EC_UNKNOWN_ERROR: An unknown error occurred in FQL
• 601 — FQL_EC_PARSER_ERROR: Error while parsing FQL statement
• 602 — FQL_EC_UNKNOWN_FIELD: The field you requested does not exist
• 603 — FQL_EC_UNKNOWN_TABLE: The table you requested does not exist
• 604 — FQL_EC_NO_INDEX: Your statement is not indexable
• 605 — FQL_EC_UNKNOWN_FUNCTION: The function you called does not exist
• 606 — FQL_EC_INVALID_PARAM: Wrong number of arguments passed into the function
• 606 — You do not have permission to fetch notifications for this user
• 606 — You can only fetch messages for one user
• 606 — Queries for these filter_keys: «nf» require a non-zero viewer that has granted read_stream permission
• 606 — uid in the where clause must be the session user
• 607 — FQL_EC_INVALID_FIELD: FQL field specified is invalid in this context.
• 608 — FQL_EC_INVALID_SESSION: An invalid session was specified
• 609 — FQL_EC_UNSUPPORTED_APP_TYPE: FQL field specified is invalid in this context.
• 610 — FQL_EC_SESSION_SECRET_NOT_ALLOWED: FQL field specified is invalid in this context.
• 611 — FQL_EC_DEPRECATED_TABLE: FQL field specified is invalid in this context.
• 612 — FQL_EC_EXTENDED_PERMISSION: The stream requires an extended permission
• 613 — FQL_EC_RATE_LIMIT_EXCEEDED: Calls to stream have exceeded the rate of 100 calls per 600 seconds.
• 614 — FQL_EC_UNRESOLVED_DEPENDENCY: Unresolved dependency in multiquery fql.multiquery
• 615 — FQL_EC_INVALID_SEARCH: This search is invalid
• 617 — FQL_EC_TOO_MANY_FRIENDS_FOR_PRELOAD: The user you queried against has too many friends to be used with Preload FQL, in order to avoid out of memory errors

Ref Errors

• 700 — API_EC_REF_SET_FAILED: Unknown failure in storing ref data. Please try again.

Application Integration Errors

• 750 — API_EC_FB_APP_UNKNOWN_ERROR: Unknown Facebook application integration failure.
• 751 — API_EC_FB_APP_FETCH_FAILED: Fetch from remote site failed.
• 752 — API_EC_FB_APP_NO_DATA: Application returned no data. This may be expected or represent a connectivity error.
• 753 — API_EC_FB_APP_NO_PERMISSIONS: Application returned user had invalid permissions to complete the operation.
• 754 — API_EC_FB_APP_TAG_MISSING: Application returned data, but no matching tag found. This may be expected.
• 755 — API_EC_FB_APP_DB_FAILURE: The database for this object failed.

Data Store API Errors

• 800 — API_EC_DATA_UNKNOWN_ERROR: Unknown data store API error
• 801 — API_EC_DATA_INVALID_OPERATION: Invalid operation
• 802 — API_EC_DATA_QUOTA_EXCEEDED: Data store allowable quota was exceeded
• 803 — API_EC_DATA_OBJECT_NOT_FOUND: Specified object cannot be found
• 804 — API_EC_DATA_OBJECT_ALREADY_EXISTS: Specified object already exists
• 805 — API_EC_DATA_DATABASE_ERROR: A database error occurred. Please try again
• 806 — API_EC_DATA_CREATE_TEMPLATE_ERROR: Unable to add FBML template to template database. Please try again.
• 807 — API_EC_DATA_TEMPLATE_EXISTS_ERROR: No active template bundle with that ID or handle exists.
• 808 — API_EC_DATA_TEMPLATE_HANDLE_TOO_LONG: Template bundle handles must contain less than or equal to 32 characters.
• 809 — API_EC_DATA_TEMPLATE_HANDLE_ALREADY_IN_USE: Template bundle handle already identifies a previously registered template bundle, and handles can not be reused.
• 810 — API_EC_DATA_TOO_MANY_TEMPLATE_BUNDLES: Application has too many active template bundles, and some must be deactivated before new ones can be registered.
• 811 — API_EC_DATA_MALFORMED_ACTION_LINK: One of more of the supplied action links was improperly formatted.
• 812 — API_EC_DATA_TEMPLATE_USES_RESERVED_TOKEN: One …or more of your templates is using a token reserved by Facebook, such as <mp3> or <video>.

Mobile/SMS Errors

• 850 — API_EC_SMS_INVALID_SESSION: Invalid sms session.
• 851 — API_EC_SMS_MSG_LEN: Invalid sms message length.
• 852 — API_EC_SMS_USER_QUOTA: Over user daily sms quota.
• 853 — API_EC_SMS_USER_ASLEEP: Unable to send sms to user at this time.
• 854 — API_EC_SMS_APP_QUOTA: Over application daily sms quota/rate limit.
• 855 — API_EC_SMS_NOT_REGISTERED: User is not registered for Facebook Mobile Texts
• 856 — API_EC_SMS_NOTIFICATIONS_OFF: User has SMS notifications turned off
• 857 — API_EC_SMS_CARRIER_DISABLE: SMS application disallowed by mobile operator

Application Information Errors

• 900 — API_EC_NO_SUCH_APP: No such application exists.

Batch API Errors

• 950 — API_BATCH_TOO_MANY_ITEMS: Each batch API can not contain more than 20 items
• 951 — API_EC_BATCH_ALREADY_STARTED: begin_batch already called, please make sure to call end_batch first.
• 952 — API_EC_BATCH_NOT_STARTED: end_batch called before begin_batch.
• 953 — API_EC_BATCH_METHOD_NOT_ALLOWED_IN_BATCH_MODE: This method is not allowed in batch mode.

Events API Errors

• 1000 — API_EC_EVENT_INVALID_TIME: Invalid time for an event.
• 1001 — API_EC_EVENT_NAME_LOCKED: You are no longer able to change the name of this event.

Info Section Errors

• 1050 — API_EC_INFO_NO_INFORMATION: No information has been set for this user
• 1051 — API_EC_INFO_SET_FAILED: Setting info failed. Check the formatting of your info fields.

LiveMessage Errors

• 1100 — API_EC_LIVEMESSAGE_SEND_FAILED: An error occurred while sending the LiveMessage.
• 1101 — API_EC_LIVEMESSAGE_EVENT_NAME_TOO_LONG: The event_name parameter must be no longer than 128 bytes.
• 1102 — API_EC_LIVEMESSAGE_MESSAGE_TOO_LONG: The message parameter must be no longer than 1024 bytes.

Credits Errors

• 1150 — API_EC_PAYMENTS_UNKNOWN: Unknown error
• 1151 — API_EC_PAYMENTS_APP_INVALID: Application is not enabled for using Facebook Credits.
• 1152 — API_EC_PAYMENTS_DATABASE: A database error occurred.
• 1153 — API_EC_PAYMENTS_PERMISSION_DENIED: Permission denied to check order details.
• 1154 — API_EC_PAYMENTS_APP_NO_RESPONSE: Payments callback to the application failed.
• 1155 — API_EC_PAYMENTS_APP_ERROR_RESPONSE: Payments callback to the application received error response.
• 1156 — API_EC_PAYMENTS_INVALID_ORDER: The supplied order ID is invalid.
• 1157 — API_EC_PAYMENTS_INVALID_PARAM: One of the Payments parameters is invalid.
• 1158 — API_EC_PAYMENTS_INVALID_OPERATION: The operation is invalid.
• 1159 — API_EC_PAYMENTS_PAYMENT_FAILED: Failed in processing the payment.
• 1160 — API_EC_PAYMENTS_DISABLED: Facebook Credits system is disabled.
• 1161 — API_EC_PAYMENTS_INSUFFICIENT_BALANCE: Insufficient balance.
• 1162 — API_EC_PAYMENTS_EXCEED_CREDIT_BALANCE_LIMIT: Exceed credit balance limit.
• 1163 — API_EC_PAYMENTS_EXCEED_CREDIT_DAILY_PURCHASE_LIMIT: Exceed daily credit purchase limit.
• 1164 — API_EC_PAYMENTS_EXCEED_CREDIT_DAILY_SPEND_LIMIT: Exceed daily credit spend limit.
• 1166 — API_EC_PAYMENTS_INVALID_FUNDING_AMOUNT: Credits purchased from funding source do not match the spend order amount.
• 1167 — API_EC_PAYMENTS_NON_REFUNDABLE_PAYMENT_METHOD: The funding source is a non-refundable payment method.
• 1168 — API_EC_PAYMENTS_USER_THROTTLED: Application is configured to throttle some users.
• 1169 — API_EC_PAYMENTS_LOGIN_REQUIRED: User is not logged in.
• 1170 — API_EC_APP_INFO_FETCH_FAILURE: Error retrieving application information.
• 1171 — API_EC_INVALID_APP_INFO: Invalid application information returned.
• 1172 — API_EC_PAYMENTS_APP_INSUFFICIENT_BALANCE: Application has insufficient balance (app2user).

Chat Errors

• 1200 — API_EC_CHAT_SEND_FAILED: An error occurred while sending the message.

Facebook Page Errors

• 1201 — API_EC_PAGES_CREATE: You have created too many pages

Facebook Links Errors

• 1500 — API_EC_SHARE_BAD_URL: The url you supplied is invalid

Facebook Notes Errors

• 1600 — API_EC_NOTE_CANNOT_MODIFY: The user does not have permission to modify this note.

Comment Errors

1700 — API_EC_COMMENTS_UNKNOWN: An unknown error has occurred.

1701 — API_EC_COMMENTS_POST_TOO_LONG: The specified post was too long.

1702 — API_EC_COMMENTS_DB_DOWN: The comments database is down.

1703 — API_EC_COMMENTS_INVALID_XID: The specified xid is not valid. xids can only contain letters, numbers, and underscores

1704 — API_EC_COMMENTS_INVALID_UID: The specified user is not a user of this application

1705 — API_EC_COMMENTS_INVALID_POST: There was an error during posting.

1706 — API_EC_COMMENTS_INVALID_REMOVE: While attempting to remove the post

2500 — Syntax error «Field id specified more than once. This is only possible before version 2.1» at character 5: id,id

Test Users

2901 — API_EC_TEST_ACCOUNTS_INVALID_ID: Test user is not associated with this app.

2902 — API_EC_TEST_ACCOUNTS_CANT_REMOVE_APP: Test user must be associated with at least one app

2903 — API_EC_TEST_ACCOUNTS_CANT_DELETE: Test user is associated with multiple apps

3000 — Reading Insights of a Page/App/Domain not owned by the querying user or application

3115 — Captcha verification failed

3301 — That code isn’t working. Please check the code and try again.

3303 — Sorry, you have made too many incorrect guesses. Please request another code.

3802 — User cannot reblock target so soon after unblocking target

3403 — Achievement hasn’t been registered for this application. See https://developers.facebook.com/docs/howtos/achievements/

3910 — You need permission to edit the details of your Business Manager. Please talk to one of your Business Manager admins about changing your role or editing the Business Manager details.

4004 — User cannot be added as an admin of this group

4006 — User cannot be removed as admin of this group»

4202 — This dialog cannot be displayed on this device

• 1363041 — Invalid upload session given.
• 1487168 — The account is invalid: The account is invalid
• 1504021 — The sharding key must be a page_id
• -3 — Please reduce the amount of data you’re asking for, then retry your request [Encountered eg when setting high limit on query to huge page feed]

Источник

Ошибка в Вайбере Registration can’t be completed Please try again later or contact

При выполнении регистрации в Вайбере мы можем столкнуться с сообщением об ошибке « Registration can’t be completed. Please try again later or contact support@viber.com ». Перезагрузка телефона, а также попытка переустановить Вайбер обычно ничего не дают, и пользователь пополняет ряды жалующихся на указанную проблему на страницах форумов и социальных сетей. Давайте разберём причины возникшей дисфункции, а также узнаем, как её можно исправить.

В чем причина ошибки Registration

В переводе текст данного сообщения звучит как «Регистрация не может быть завершена. Пожалуйста, попробуйте позже или свяжитесь со службой поддержки по адресу support@viber.com»

При этом многочисленные обращения пользователей в службу поддержки часто не дают какого-либо результата. В ответ приходят стандартные отписки, без каких-либо советов по решению проблемы. Обычно поддержка указывает, что они отправили активационное сообщение на мобильный номер пользователя, при этом пользователь попросту не получает данное смс .

Причинами ошибки обычно является следующее:

• Нестабильное сетевое соединение;
• Сбой в работе серверов Вайбера;
• Некорректная установка Вайбера на телефоне;
• Проблемы в работе мобильного оператора, вследствие чего активационное смс не может быть доставлено;
• Попытка регистрации Вайбера с помощью ПК;
• Мобильный номер пользователя для регистрации уже был использован ранее.

Давайте разберёмся, как исправить ошибку «Registration can’t be completed» в Вайбере.

Убедитесь в стабильности вашего Интернет-соединения

Первым делом убедитесь, что у вас не наблюдается проблем в работе сети . Посетите любимые странички и убедитесь, что они загружаются.

Подождите какое-то время

Довольно часто причиной дисфункции «Please try again later or contact support@viber.com» в Вайбере является сбой в работе серверов Вайбера . Рекомендуем посетить ресурс , и убедиться, что с приложением не наблюдается массовых проблем.

Проверьте отсутствие жалоб у пользователей

Если таковых нет, подождите какое-то время (от нескольких часов до суток), и попробуйте вновь пройти процедуру регистрации . Часто лишь ожидание становится способом решить указанную проблему.

Очистите кэш приложения Вайбера

Также рекомендуем очистить кэш вашего Вайбера. Для этого перейдите в настройки вашего гаджета, выберите там « Приложения », и найдите « Viber ». Тапните по нём, и войдя в его опции, нажмите на « Остановить », а затем на « Очистить кэш ».

После выполнения указанной процедуры перегрузите ваш девайс , и попробуйте вновь пройти процедуру регистрации в Вайбере.

Используйте мобильное приложение

Проходите регистрацию в Вайбере исключительно на мобильном гаджете. После благополучного завершения процедуры можно устанавливать и десктопную версию Вайбера, подтвердив регистрацию с помощью сканирования QR-кода .

Перегрузите ваш девайс для устранения ошибки

В некоторых случаях проблемы с качеством мобильной сети могут вызывать рассматриваемую в статье ошибку. Рекомендуем перезагрузить ваше мобильное устройство и проверить его в работу при приёме смс. Если смс проходят нормально, тогда идём дальше.

Скачайте актуальную версию Вайбера

Сбои при загрузке и установке Вайбера (а также использование его устаревшей версии) могут вызывать рассматриваемую нами проблему. Скачайте актуальную версию продукта (Андроид, iOS), и попробуйте вновь пройти процедуру регистрации.

Попробуйте другой номер

Если имеется возможность, попробуйте для регистрации в Вайбере использовать другой мобильный номер. Возможно, ваш номер уже был использован ранее, потому выполнить регистрацию на него не представляется возможным.

Смените язык телефона на английский, чтобы избавиться от сообщения

Некоторым пользователям избавиться от ошибки помогла установка языка телефона на английский . После этого регистрация проходила без каких-либо проблем, а после удачного завершения оной вы можете легко поменять язык телефона обратно на русский.

Обратитесь в службу поддержки

Ну и, конечно же, можно последовать совету, указанному в сообщении, и написать в службу поддержки по адресу support@viber.com. Но учтите, что эффективность такой переписки обычно невелика.

Заключение

В нашем материале мы разобрали причины распространенной ошибки при регистрации в Вайбере «Registration can’t be completed Please try again later or contact», а также перечислили способы, позволяющие её исправить. Во многих случаях основным фактором проблемы становился сбои серверов Вайбера, вследствие чего пользователь не получает активационное смс. Рекомендуем подождать какое-то время, пока функционал серверов не будет восстановлен, и вы сможете пройти регистрацию в стандартном формате.

Источник

phwd/fbec

Use Git or checkout with SVN using the web URL.

Work fast with our official CLI. Learn more.

Sign In Required

Please sign in to use Codespaces.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

Git stats

Files

Failed to load latest commit information.

readme.md

Facebook API Error Codes for Developers

This list is heavily based on

Should this stay in table format? Seems quite unbearable to keep it handled in tables. Also I didn’t take into account «Generated by methods»

General Errors

• 0 — API_EC_SUCCESS: Success
• 1 — API_EC_UNKNOWN: An unknown error occurred
• 2 — API_EC_SERVICE: Service temporarily unavailable
• 3 — API_EC_METHOD: Unknown method
• 4 — API_EC_TOO_MANY_CALLS: Application request limit reached
• 5 — API_EC_BAD_IP: Unauthorized source IP address
• 6 — API_EC_HOST_API: This method must run on api.facebook.com
• 7 — API_EC_HOST_UP: This method must run on api-video.facebook.com
• 8 — API_EC_SECURE: This method requires an HTTPS connection
• 9 — API_EC_RATE: User is performing too many actions
• 10 — API_EC_PERMISSION_DENIED: Application does not have permission for this action
• 10 — User cannot edit action
• 10 — User cannot delete action
• 10 — Not a Messenger client
• 10 — Error creating monetization property
• 10 — The app updating this status card must be the same one that created the corresponding page’s CTA.
• 10 — This setting was in an unexpected state, and could not be enabled.
• 10 — Request is not from facebook IOS app
• 10 — User is not mentioned in the caption
• 11 — API_EC_DEPRECATED: This method is deprecated
• 12 — API_EC_VERSION: This API version is deprecated
• 13 — API_EC_INTERNAL_FQL_ERROR: The underlying FQL query made by this API call has encountered an error. Please check that your parameters are correct.
• 14 — API_EC_HOST_PUP: This method must run on api-photo.facebook.com
• 15 — API_EC_SESSION_SECRET_NOT_ALLOWED: This method call must be signed with the application secret (You are probably calling a secure method using a session secret)
• 16 — API_EC_HOST_READONLY: This method cannot be run on this host, which only supports read-only calls
• 17 — API_EC_USER_TOO_MANY_CALLS: User request limit reached
• 18 — API_EC_REQUEST_RESOURCES_EXCEEDED: This API call could not be completed due to resource limits
• 20 — This API call does not support the requested response format
• 27 — This app does not have permission to manage this Facebook at Work account.

OAuthException

• 30 — Duplicate Fundraiser — sub-code — 1965015 — This fundraiser is identical to the last one you created. Try visiting your timeline to see your fundraiser, or delete your previous fundraiser.

Parameter Errors

• 100 — Something is wrong
• 100 — API_EC_PARAM: Invalid parameter
• 100 — No permission to publish the video
• 100 — Cannot post to User Likes with Page Access Token
• 100 — Parameters do not match any fields that can be updated
• 100 — Object does not support message editing
• 100 — Please enter a valid email address
• 100 — Comment not found
• 100 — url should represent a valid URL
• 100 — inst_type must be one of the following values: CreditCard, ApplePayCard
• 100 — Unsupported post request. Object with ID ‘me’ does not exist, cannot be loaded due to missing permissions, or does not support this operation. Please read the Graph API documentation at https://developers.facebook.com/docs/graph-api
• 100 — Must be a valid ISO 4217 currency code
• 100 — Param preferred_thumbnail_id must be a thumbnail of this video.
• 100 — Param tid must be a thread id, thread fbid, or canonical id
• 100 — The page is not qualified to use Video Copyright API. Please verify that the page has completed Video Copyright API onboarding process.
• 100 — Employee Account or Specific App Conditions
• 101 — API_EC_PARAM_API_KEY: Invalid API key
• 102 — API_EC_PARAM_SESSION_KEY: Session key invalid or no longer valid
• 103 — API_EC_PARAM_CALL_ID: Call_id must be greater than previous
• 104 — API_EC_PARAM_SIGNATURE: Incorrect signature
• 105 — API_EC_PARAM_TOO_MANY: The number of parameters exceeded the maximum for this operation
• 110 — API_EC_PARAM_USER_ID: Invalid user id
• 111 — API_EC_PARAM_USER_FIELD: Invalid user info field
• 112 — API_EC_PARAM_SOCIAL_FIELD: Invalid user field
• 113 — API_EC_PARAM_EMAIL: Invalid email
• 114 — API_EC_PARAM_USER_ID_LIST: Invalid user ID list
• 114 — An id must be a valid ID string (e.g., «123»)
• 115 — API_EC_PARAM_FIELD_LIST: Invalid field list
• 120 — API_EC_PARAM_ALBUM_ID: Invalid album id
• 121 — API_EC_PARAM_PHOTO_ID: Invalid photo id
• 130 — API_EC_PARAM_FEED_PRIORITY: Invalid feed publication priority
• 140 — API_EC_PARAM_CATEGORY: Invalid category
• 141 — API_EC_PARAM_SUBCATEGORY: Invalid subcategory
• 142 — API_EC_PARAM_TITLE: Invalid title
• 143 — API_EC_PARAM_DESCRIPTION: Invalid description
• 145 — API calls from the server require an appsecret_proof argument
• 144 — API_EC_PARAM_BAD_JSON: Malformed JSON string
• 150 — API_EC_PARAM_BAD_EID: Invalid eid
• 151 — API_EC_PARAM_UNKNOWN_CITY: Unknown city
• 152 — API_EC_PARAM_BAD_PAGE_TYPE: Invalid page type
• 170 — API_EC_PARAM_BAD_LOCALE: Invalid locale
• 180 — API_EC_PARAM_BLOCKED_NOTIFICATION: This notification was not delieved
• 190 — API_EC_PARAM_ACCESS_TOKEN: Invalid OAuth 2.0 Access Token
• 190 — The access token does not match the user claiming the offer
• 190 — The access token does not match the user resending the offer
• 193 — The time specified is too far back in the past. Please do a full refresh of the friends using the friend FQL table

User Permission Errors

• 200 — API_EC_PERMISSION: Permissions error
• 200 — User does not have permission to post to target
• 200 — Video is either deleted or you do not have permission to view it
• 200 — This post wasn’t created by the application
• 200 — Posts where the actor is a page cannot also include a target_id other than EVENT or GROUP»
• 200 — Subject does not have permission to create live video on this page
• 200 — Subject does not have permission to create live video on this user
• 210 — API_EC_PERMISSION_USER: User not visible
• 211 — API_EC_PERMISSION_NO_DEVELOPERS: Application has no developers.
• 212 — API_EC_PERMISSION_OFFLINE_ACCESS: Renewing a session offline requires the extended permission offline_access
• 220 — API_EC_PERMISSION_ALBUM: Album or albums not visible
• 220 — User cannot delete this album.
• 221 — API_EC_PERMISSION_PHOTO: Photo not visible
• 230 — API_EC_PERMISSION_MESSAGE: Permissions disallow message to user
• 240 — API_EC_PERMISSION_MARKUP_OTHER_USER: Desktop applications cannot set FBML for other users
• 240 — This user isn’t allowed to upload photos to this object’s wall
• 250 — API_EC_PERMISSION_STATUS_UPDATE: Updating status requires the extended permission status_update.
• 260 — API_EC_PERMISSION_PHOTO_UPLOAD: Modifying existing photos requires the extended permission photo_upload
• 261 — API_EC_PERMISSION_VIDEO_UPLOAD: Modifying existing photos requires the extended permission photo_upload
• 270 — API_EC_PERMISSION_SMS: Permissions disallow sms to user.
• 270 — Development access is not allowed to access business API post:Business/adaccount.
• 273 — This Ads API call requires the user to be admin of the ad account. User not admin on ad account
• 275 — Reading advertisements requires an access token with the extended permission ads_read
• 280 — API_EC_PERMISSION_CREATE_LISTING: Creating and modifying listings requires the extended permission create_listing
• 281 — API_EC_PERMISSION_CREATE_NOTE: Managing notes requires the extended permission create_note.
• 282 — API_EC_PERMISSION_SHARE_ITEM: Managing shared items requires the extended permission share_item.
• 290 — API_EC_PERMISSION_EVENT: Creating and modifying events requires the extended permission create_event
• 291 — API_EC_PERMISSION_LARGE_FBML_TEMPLATE: FBML Template isn’t owned by your application.
• 292 — API_EC_PERMISSION_LIVEMESSAGE: An application is only allowed to send LiveMessages to users who have accepted the TOS for that application.
• 293 — API_EC_PERMISSION_XMPP_LOGIN: Logging in to chat requires the extended permission xmpp_login
• 294 — API_EC_PERMISSION_ADS_MANAGEMENT: Managing advertisements requires the extended permission ads_management, and a participating API key
• 296 — API_EC_PERMISSION_CREATE_EVENT: Managing events requires the extended permission create_event
• 298 — API_EC_PERMISSION_READ_MAILBOX: Reading mailbox messages requires the extended permission read_mailbox
• 299 — API_EC_PERMISSION_RSVP_EVENT: RSVPing to events requires the extended permission create_rsvp

Data Editing Errors

• 300 — API_EC_EDIT: Edit failure
• 310 — API_EC_EDIT_USER_DATA: User data edit failure
• 320 — API_EC_EDIT_PHOTO: Photo edit failure
• 320 — This photo is not wide enough to use as a Timeline Cover, the minimum width is 399 pixels
• 321 — API_EC_EDIT_ALBUM_SIZE: Album is full
• 322 — API_EC_EDIT_PHOTO_TAG_SUBJECT: Invalid photo tag subject
• 323 — API_EC_EDIT_PHOTO_TAG_PHOTO: Cannot tag photo already visible on Facebook
• 324 — API_EC_EDIT_PHOTO_FILE: Missing or invalid image file
• 325 — API_EC_EDIT_PHOTO_PENDING_LIMIT: Too many unapproved photos pending
• 326 — API_EC_EDIT_PHOTO_TAG_LIMIT: Too many photo tags pending
• 327 — API_EC_EDIT_ALBUM_REORDER_PHOTO_NOT_IN_ALBUM: Input array contains a photo not in the album
• 328 — API_EC_EDIT_ALBUM_REORDER_TOO_FEW_PHOTOS: Input array has too few photos
• 329 — API_EC_MALFORMED_MARKUP: Template data must be a JSON-encoded dictionary, of the form
• 330 — API_EC_EDIT_MARKUP: Failed to set markup
• 340 — API_EC_EDIT_FEED_TOO_MANY_USER_CALLS: Feed publication request limit reached
• 341 — API_EC_EDIT_FEED_TOO_MANY_USER_ACTION_CALLS: Feed action request limit reached
• 342 — API_EC_EDIT_FEED_TITLE_LINK: Feed story title can have at most one href anchor
• 343 — API_EC_EDIT_FEED_TITLE_LENGTH: Feed story title is too long
• 344 — API_EC_EDIT_FEED_TITLE_NAME: Feed story title can have at most one fb:userlink and must be of the user whose action is being reported
• 345 — API_EC_EDIT_FEED_TITLE_BLANK: Feed story title rendered as blank
• 346 — API_EC_EDIT_FEED_BODY_LENGTH: Feed story body is too long
• 347 — API_EC_EDIT_FEED_PHOTO_SRC: Feed story photo could not be accessed or proxied
• 348 — API_EC_EDIT_FEED_PHOTO_LINK: Feed story photo link invalid
• 350 — API_EC_EDIT_VIDEO_SIZE: Video file is too large
• 351 — API_EC_EDIT_VIDEO_INVALID_FILE: Video file was corrupt or invalid
• 352 — API_EC_EDIT_VIDEO_INVALID_TYPE: Video file format is not supported
• 353 — API_EC_EDIT_VIDEO_FILE: Missing video file
• 354 — API_EC_EDIT_VIDEO_NOT_TAGGED: User is not tagged in this video
• 355 — API_EC_EDIT_VIDEO_ALREADY_TAGGED: User is already tagged in this video
• 360 — API_EC_EDIT_FEED_TITLE_ARRAY: Feed story title_data argument was not a valid JSON-encoded array
• 361 — API_EC_EDIT_FEED_TITLE_PARAMS: Feed story title template either missing required parameters, or did not have all parameters defined in title_data array
• 362 — API_EC_EDIT_FEED_BODY_ARRAY: Feed story body_data argument was not a valid JSON-encoded array
• 363 — API_EC_EDIT_FEED_BODY_PARAMS: Feed story body template either missing required parameters, or did not have all parameters defined in body_data array
• 364 — API_EC_EDIT_FEED_PHOTO: Feed story photos could not be retrieved, or bad image links were provided
• 365 — API_EC_EDIT_FEED_TEMPLATE: The template for this story does not match any templates registered for this application
• 366 — API_EC_EDIT_FEED_TARGET: One or more of the target ids for this story are invalid. They must all be ids of friends of the acting user
• 367 — API_EC_EDIT_FEED_MARKUP: The template data provided doesn’t cover the entire token set needed to publish the story
• 368 — The action attempted has been deemed abusive or is otherwise disallowed
• 370 — API_EC_USERS_CREATE_INVALID_EMAIL: The email address you provided is not a valid email address
• 371 — API_EC_USERS_CREATE_EXISTING_EMAIL: The email address you provided belongs to an existing account
• 372 — API_EC_USERS_CREATE_BIRTHDAY: The birthday provided is not valid
• 373 — API_EC_USERS_CREATE_PASSWORD: The password provided is too short or weak
• 374 — API_EC_USERS_REGISTER_INVALID_CREDENTIAL: The login credential you provided is invalid.
• 375 — API_EC_USERS_REGISTER_CONF_FAILURE: Failed to send confirmation message to the specified login credential.
• 376 — API_EC_USERS_REGISTER_EXISTING: The login credential you provided belongs to an existing account
• 377 — API_EC_USERS_REGISTER_DEFAULT_ERROR: Sorry, we were unable to process your registration.
• 378 — API_EC_USERS_REGISTER_PASSWORD_BLANK: Your password cannot be blank. Please try another.
• 379 — API_EC_USERS_REGISTER_PASSWORD_INVALID_CHARS: Your password contains invalid characters. Please try another.
• 380 — API_EC_USERS_REGISTER_PASSWORD_SHORT: Your password must be at least 6 characters long. Please try another.
• 381 — API_EC_USERS_REGISTER_PASSWORD_WEAK: Your password should be more secure. Please try another.
• 382 — API_EC_USERS_REGISTER_USERNAME_ERROR: Our automated system will not approve this name.
• 383 — API_EC_USERS_REGISTER_MISSING_INPUT: You must fill in all of the fields.
• 384 — API_EC_USERS_REGISTER_INCOMPLETE_BDAY: You must indicate your full birthday to register.
• 385 — API_EC_USERS_REGISTER_INVALID_EMAIL: Please enter a valid email address.
• 386 — API_EC_USERS_REGISTER_EMAIL_DISABLED: The email address you entered has been disabled. Please contact disabled@facebook.com with any questions.
• 387 — API_EC_USERS_REGISTER_ADD_USER_FAILED: There was an error with your registration. Please try registering again.
• 388 — API_EC_USERS_REGISTER_NO_GENDER: Please select either Male or Female.

Authentication Errors

• 400 — API_EC_AUTH_EMAIL: Invalid email address
• 401 — API_EC_AUTH_LOGIN: Invalid username or password
• 402 — API_EC_AUTH_SIG: Invalid application auth sig
• 403 — API_EC_AUTH_TIME: Invalid timestamp for authentication
• 411 — The user is not allowed to log into this app
• 412 — User has not installed the application

Session Errors

• 450 — API_EC_SESSION_TIMED_OUT: Session key specified has passed its expiration time
• 451 — API_EC_SESSION_METHOD: Session key specified cannot be used to call this method
• 452 — API_EC_SESSION_INVALID: Session key invalid. This could be because the session key has an incorrect format, or because the user has revoked this session
• 453 — API_EC_SESSION_REQUIRED: A session key is required for calling this method
• 454 — API_EC_SESSION_REQUIRED_FOR_SECRET: A session key must be specified when request is signed with a session secret
• 455 — API_EC_SESSION_CANNOT_USE_SESSION_SECRET: A session secret is not permitted to be used with this type of session key
• 456 — The session is malformed
• 457 — The session has an invalid origin
• 458 — User USER_ID has not authorized application APP_ID
• 459 — The user has been checkpointed. The error_data will contain the URL the user needs to go to to clear the checkpoint
• 460 — Session does not match current stored session. This may be because the user changed the password since the time the session was created or Facebook has changed the session for security reasons
• 461 — Session is invalid. This could be because the application was uninstalled after the session was created
• 462 — The session has a stale version
• 464 — The session user is not confirmed
• 463 — Session has expired at unix time SOME_TIME. The current unix time is SOME_TIME
• 465 — The session user is invalid
• 466 — The session was invalidated explicitly using an API call
• 467 — The session is invalid because the user logged out
• 468 — The session is invalid, because the user has not used the app for a long time
• 478 — The images you tried to upload are too many

Application Messaging Errors

500 — API_EC_MESG_BANNED: Message contains banned content

501 — API_EC_MESG_NO_BODY: Missing message body

502 — API_EC_MESG_TOO_LONG: Message is too long

503 — API_EC_MESG_RATE: User has sent too many messages

Источник