Platform connection
Introduction
Event sending to the platform is done with the Tracking Component.
It is responsible for tracking and monitoring the information obtained during the execution of the operations. Real-time tracking of this data will be possible on the Platform, while the process is running on the client's device.
Unlike the rest, this component does not work independently; it works transversally to the rest of the components installed in the SDKMobile.
In the section of Simplified Launch the necessary steps for the basic SDK Integration are detailed. This section adds the information for the launch of this component.
Dependency
The specific dependency for the component is:
implementation "com.facephi.androidsdk:tracking_component:$version"Available controllers
Controller
Description
TrackingController
Main Tracking controller
TrackingErrorController
Controller to manage the possible errors that occur
ExtraDataController
Controller to obtain the ExtraData which allows the communication from the client to the server with SelphIDSdk installed.
Simplified Launch
The controller must be included during SDK Initialization.
Error handling
The callback can be configured to control Tracking errors:
Advanced information
Additional controllers
ExtraDataController
This controller (ExtraDataController) allows obtaining an identifier for the current operation. This data will be sent to the backend where the relevant checks will be performed.
The call to obtain the extraData, needs the information of the current operation, which requires that it has been previously performed a newOperation.
Error reception
In the error section, we will have the TrackingError class. The class will return 3 fields:
name: String with the error name
error: Additional information if necessary
stepType: SDK component in which the event sending failed
List of errors:
APPLICATION_CONTEXT_ERROR: Error in context initialization
ASSET_LINK: Error when sending the resource link
ASSET_UPLOAD: Error during resource upload
COMPONENT_LICENSE_ERROR: Component License missing or invalid
CUSTOMER_ID: Error when obtaining or validating the customer ID
DEVICE_EVENT_ERROR: Failure during a device-related event
EMPTY_LICENSE: Empty or nonexistent License data
FLOW: Error during the execution Flow
INITIALIZATION_ERROR: General failure in Initialization
INIT_IDS_ERROR: Error when generating or assigning IDs during Initialization
INIT_OPERATION: Failed operation in the Initialization phase
LICENSE_ERROR: Invalid or corrupted License
MANAGER_NOT_INITIALIZED: The manager was used without initializing it
NETWORK_CONNECTION: Problem with the network connection
NETWORK_ERROR: Generic network failure
NO_OPERATION_CREATED_ERROR: No operation was created when one was expected
OCR_DATA: Error processing OCR data
OPERATION_NOT_CREATED: The expected operation was not generated
OPERATION_ID: Invalid or missing operation ID
SESSION_ID: Error with the session identification
SIGNATURE_RESULT: Failure in the signature process or result
STEP_CHANGE: Unexpected or invalid step transition
STEP_RESULT_CANCELLED: The step was unexpectedly cancelled
STEP_RESULT_ERROR: The step ended with an error
STEP_RESULT_EXPIRED: The step result expired before completion
STEP_RESULT_SUCCEEDED: The step succeeded but generated an unexpected issue
TOKEN_ERROR: Token missing, expired or invalid
ADVANCED_TRACKING_UPLOAD: Failure when uploading advanced Tracking data
TENANT_ID_EMPTY_ERROR: The tenant ID was empty or missing
ADVANCED_TRACKING_SERIALIZATION_ERROR: Error serializing advanced Tracking data
ADVANCED_TRACKING_VALIDATION_ERROR: Failure in Tracking data validation
TOKENIZER_ERROR: Error during the tokenization process
Last updated