ActivityResultContract, so the outcome comes back the
same way any other activity result does.
Compose
ViewModel, not in the composable. It has to survive
configuration changes, and a composable is re-run for reasons that have nothing to do with
the user asking to verify:
Views
Fragment. Register it as a field there too.
Fetching the token
The token comes from your backend, over your own authenticated endpoint:Adding configuration
Pass anSdkConfig to control appearance, copy and capture behaviour. Every field has a
default, so SdkConfig() is valid:
Next
Handling the result
Every outcome, every error code, and surviving process death.

