<provider\n android:name=\"androidx.startup.InitializationProvider\"\n android:authorities=\"${applicationId}.androidx-startup\"\n android:exported=\"false\"\n tools:node=\"merge\">\n <meta-data android:name=\"com.adyen.ipp.api.InPersonPaymentsInitializer\"\n tools:node=\"remove\" \/>\n <\/provider><\/code><\/pre>\nTo manually initialize that component at a later point, add the following code to the POS app.<\/p>\n
For Mobile SDK version 2.6.0 or later:<\/p>\n
Since the SDK requires the application to be in the foreground to bind to the service, you need to trigger initialization when your main Activity is visible. Use repeatOnLifecycle<\/code> to ensure that the initialization runs when the Activity is in the RESUMED<\/code> state. <\/p>\noverride fun onCreate(savedInstanceState: Bundle?) {\n super.onCreate(savedInstanceState)\n\n lifecycleScope.launch {\n \/\/ Suspend execution until the Activity is RESUMED\n repeatOnLifecycle(Lifecycle.State.RESUMED) {\n val state = InPersonPaymentsTools.initializeManually(this@MainActivity)\n\n if (state is InitializationState.SuccessfulInitialization) {\n \/\/ SDK is ready\n } else {\n \/\/ Handle failure\n }\n }\n }\n}<\/code><\/pre>\nFor Mobile SDK versions earlier than version 2.6.0:<\/p>\n
AppInitializer.getInstance(this)\n .initializeComponent(InPersonPaymentsInitializer::class.java)<\/code><\/pre>\nInitialization status check<\/h3>\n
To check the status of the SDK initialization, you can use one of the following options.<\/p>\n
For Mobile SDK version 2.6.0 or later:<\/p>\n
when (val state = InPersonPaymentsTools.getInitializationState()){\n InitializationState.SuccessfulInitialization -> {\n \/\/ SDK is ready. You can now safely proceed.\n }\n\n is InitializationState.FailedInitialization -> {\n \/\/ Handle initialization failure. Log errors or notify the user.\n Log.e(\"MyApp\", \"SDK initialization failed: ${state.failureReasons}\")\n }\n\n else -> Unit\n}<\/code><\/pre>\nor for Mobile SDK versions earlier than version 2.6.0 if you need more precise control over the state flow:<\/p>\n
InPersonPayments.initialized\n .filter { it == InitializationState.SuccessfulInitialization } \/\/ Wait until it is true.\n .take(1) \/\/ Take only one item.\n .collect { ready ->\n if (ready) {\n val id = InPersonPayments.getInstallationId()\n \/\/...\n }\n }<\/code><\/pre>\nManage POS app dependency initialization<\/h3>\n
The code that you add to the Application.onCreate()<\/code> method is executed for all processes. In some cases, it can be beneficial to skip the re-execution of the code, for example the initialization of your dependency graph or analytics libraries.<\/p>\nThe following method evaluates specific conditions and returns a boolean value that indicates whether the initialization should be skipped.<\/p>\n
if (InPersonPaymentsTools.shouldSkipAppInitialize(context)) {\n \/\/ Perform actions when initialization should be skipped\n} else {\n \/\/ Proceed with application initialization\n}<\/code><\/pre>\nAdditionally, you can use the following functions:<\/p>\n
\n- \n
suspend InPersonPaymentsTools.getInitializationState()<\/code>: this function observes the initialization state of the SDK and pauses the calling coroutine until the SDK initialization finishes and reaches a success or failure state. You can use this suspend function if an action in your app depends on the SDK being fully initialized.<\/p>\n<\/li>\n- \n
suspend InPersonPaymentsTools.initializeManually()<\/code>: this function triggers initialization of the SDK and waits for the initialization to finish.<\/p>\n<\/li>\n<\/ul>\n4. Use the warm-up function<\/h2>\n
To speed up initiating transactions, you can use the warm-up function. This function checks for a session, configuration changes, and security checks if needed.<\/p>\n
As a best practice, call the warm-up function after the SDK has initialized:<\/p>\n