Mobbeel for developers

Mobbeel for developers

  • MobbScan
  • MobbID
  • MobbSign
  • Clients
  • FAQ

›Getting Started

MobbScan iOS

  • Welcome to the MobbScan SDK
  • SDK size

Configure SDK

  • Configure the iOS SDK

Migration Guides

  • Migration to 2.26.0
  • Migration to 2.19.0
  • Migration to 2.18.0
  • Migration to 2.17.0
  • Migration to 2.16.0

Getting Started

  • Initalize API
  • Scanning a document with MobbScan
  • Performing Face Matching
  • Adding a video step
  • Record a video while user scans the document
  • Getting the verification result
  • Scanning documents with NFC
  • Detect and scan MRZ
  • Detect and scan a PDF417
  • Add fields to validations in agent portal
  • Error Handling

Additional Configuration

  • MobbScan Configuration

Customization

  • Customize Detection Views
  • Customize Feedback Messages
  • Customize Unattended Process

Reference

  • Changelog

Error Handling

Overview

As you might have read along these documents, most of the MobbScanAPI callbacks have an error as their last argument. This is the way MobbScan let you know the reason why a process did not end successfully.

The possible error comes in the form of a NSError where:

  • code: is a Int which value matches the enum type MobbScanAPIErrorCode
  • userInfo: is a Dictionary with further information, with both keys and values of type String

Error Codes

The following table shows the possible error codes and their meaning:

CodeMeaning
SCANNING_PROCESS_CANCELLEDThe user cancelled the scanning process
CONNECTION_ERRORA network connection error happened
LICENSE_ERRORThe license is not valid or has not been configured
WRONG_PARAMETERS_ERRORSome of the parameters are not valid
SCAN_PROCESS_NOT_STARTEDThe scan process has not been started
SCAN_ID_DOES_NOT_MATCHThe provided scan id does not match the currently started scan
DEVICE_NOT_COMPATIBLEDevice does not fulfill the minimum requirements
UNEXPECTED_ERRORSomething unexpected happened during the process
API_NOT_INITIALIZEDMobbScanAPI was not properly initialised
CAMERA_NOT_VALID_FOR_VALIDATIONDevice camera does not fulfill the needed specs
NOT_AVAILABLE_IN_OFFLINE_MODEThe process is only available online
CAPTURE_FACE_ERRORFacial detection could not accomplished
PROCESS_CANCELLEDThe user cancelled any process (document detection, face validation...)
TIMEOUT_ERRORThe process timeout expired
ANTISPOOFING_ERRORThe antispoofing mechanism cannot ensure the user is genuine
DOCUMENT_NOT_CLASSIFIEDThe system is not able to classify the document (only applicable for generic document types, i.e. ESP)
DOCUMENT_NOT_VALIDThe document did not pass the validations (applicable when specific validations are activated)
PERMISSION_ERRORThe user has denied some of the required permissions
UNAUTHORIZEDThis user is not authorized to perform the requested action

Extra Information

As mentioned above, chances are that a process may need to expose further information about an error. This is an example of what you would get for a scan process when the validations failed:

Swift
ObjectiveC
if let error = error {
print("Failed validations: \((error as NSError).userInfo["extraInfo"] ?? "")")
}
NSLog(@"Failed validations: %@", [[error userInfo] valueForKey:@"extraInfo"]);

The console will print:

Failed validations: validationMRZ, validationDocumentNotExpired, validationBothSidesMatchScore
← Add fields to validations in agent portalMobbScan Configuration →
  • Overview
  • Error Codes
  • Extra Information
Mobbeel for developers
Product Documentation
MobbIDMobbScanMobbSign
Connect
LinkedInFacebookX
More
FAQContact Us
Mobbeel Solutions SL
Copyright © 2025 Mobbeel Solutions SL