Symptom
The Business APIs [1] interrupt pedingVerification provided by the mobile SDK may pass an empty regToken as a parameter to the Business API caller.
Also, if there are multiple interruptions on the server side, it has to be in use the old regToken
Example: the REST API accounts.finalizeRegistration has the following response [2]:
If the CDC SDK has logic that expects the response of a REST API"accounts.finalizeRegistration" to contain a regToken, is it a bug in the CDC SDK or the REST API "accounts.finalizeRegistration"?
[1]Business APIs
https://sap.github.io/gigya-swift-sdk/GigyaSwift/#business-apis
[2]API accounts.finalizeRegistration Response
"errorDetails": "Account Pending Verification",
"errorMessage": "Account Pending Verification",
SWIFT SDK Source
https://github.com/SAP/gigya-swift-sdk/blob/main/GigyaSwift/Global/Resolvers/InterruptionResolverFactory.swift#L44
Read more...
Environment
- SAP Customer Data Cloud
- Mobile SDK
- Web SDK
Product
Keywords
Gigya, CDC, pendingRegistration, regToken, SWIFT SDK, Multiple interruptions , KBA , CEC-PRO-MOB , Mobile (Swift, Android, Native Screen-Sets) , How To
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview