ASAPPUser
with a null customer identifier. However, many chat use cases might require ASAPP to know the identity of the user.
To connect as an identified user, please specify a customer identifier string and a request context provider function. This provider will be called from a background thread, when the SDK makes requests that require customer authentication with your company’s servers. The request context provider is a function that returns a map with keys and values agreed upon with ASAPP. Please ask your Implementation Manager if you have questions.
ASAPPUserLoginHandler
to call to the application. Due to the asynchronous nature of this flow, your application should use the activity lifecycle to provide a result to the SDK.
How to Implement the Sign In Flow
ASAPPUserLoginHandler
and start your application’s LoginActivity
, including the given request code.
LoginActivity
with Activity.RESULT_OK
.
LoginActivity
with Activity.RESULT_CANCELED
.
LoginActivity
finishes, the SDK will capture the result and resume the chat conversation.
refreshContext
parameter set to true
indicating that the context must be refreshed. In that case, please make sure to return a map with fresh credentials that can be used to authenticate the user. In case an API call is required to refresh the credentials, make sure to block the calling thread until the updated context can be returned.