Social Login: Apple missing errorDetails

[SarahSteininger]

If I use gigya.login with Apple as a provider, the response I receive in onPending does not include the missing required fields for registration.
gigya.login(GigyaDefinitions.Providers.APPLE ...)

Social Sign In with Apple:
{"errorCode":206001,"errorMessage":"Account Pending Registration","regToken":"....."}

Social Sign in with Google (expected response containing missing fields):
{ "callId": "...", "errorCode": 206001, "errorDetails": "Missing required fields for registration: country, preferences...", "errorMessage": "Account Pending Registration", "apiVersion": 2, "statusCode": 206, "statusReason": "Partial Content", "time": "2021-04-08T09:06:05.148Z", "newUser": false, "accountInfo": “ ...

[tal-mi]

Hi,

Can you please provide a callID for that error?

[SarahSteininger]

Unfortunately there is no callId in the response when I try to login with apple as a provider. Below you find the whole response I get.
{"errorCode":206001,"errorMessage":"Account Pending Registration","regToken":"....."}

[tal-mi]

Do you have a network capture?

[SarahSteininger]

Network profiling data is unavailable.

[tal-mi]

Network capture as in .har file? Using Filddler or Charles.
I will investigate this further.
Thanks.

Tal.

[SarahSteininger]

Thanks.
Moreover I would like to pass the missing consent upon social login as we do ask for the consent before calling login.
It seems that the consent I pass is completely ignored as the consent is still part of the missing fields in onPending.

gigya.login(
socialProvider, consent,
object : GigyaLoginCallback() { .....

callId: 32217a6ef142423e92beddeb6193d3aa

[tal-mi]

Are u utilizing the "onPendingRegistration" callback to resolve it?
If you are looking to resolve your login flow given a missing fields error, we have provided this callback just for that.
The callback will return a IPendingRegistrationResolver class which can be used to call setAccount with the missing fields required for the process to end successfully.

To make sure you are receiving the missing fields make sure you add "missing-required-fields" to your "include" parameter.
Or use the account config feature.

[SarahSteininger]

I know how to handle missing fields in onPending, however my question is why does passing the consent as a parameter of the login call not work.

When I call register, I can pass the consent in params.

If I try the same when I call login with social provider, the consent I pass as a parameter is ignored.

[tal-mi]

What kind of "consent" parameters are you passing through?

[SarahSteininger]

Terms of Service and other consent statements.
I wrap them inside a preferences map (for example: terms.myTerms.basic.isConsentGranted).

[tal-mi]

Thank you. Ill investigate the issue and update as soon as I can.

Tal

[tal-mi]

Hi,

The reason consent is not applied when using social login is because it is not supported via that specific endpoint.
It is recommended that you do it using setAccountInfo with the "regToken" you receive.
I will raise this issue with our backend team.

[SarahSteininger]

Thanks!
Actually what is expected to be passed when using social login? Without the consent I have nothing to pass, but passing an empty map is not supported (however this is possible in the swift SDK: gigya.login(with: provider, viewController: viewController) ...).

java.lang.UnsupportedOperationException: Operation is not supported for read-only collection
at kotlin.collections.EmptyMap.put(Unknown Source:4)
at com.gigya.android.sdk.api.BusinessApiService.login(BusinessApiService.java:206)
at com.gigya.android.sdk.Gigya.login(Gigya.java:388)

[tal-mi]

Social login requires the provider. Additional params may include "lang". Consent params are not supported.

Passing empty map to Gigya.login call is not supported cause you require to pass credentials in order to log in.

Tal.

[SarahSteininger]

Hi Tal,
Did you have any luck on figuring out why we get the error message without the missing fields?
I guess this issue is related to the non native webview logins as we are experiencing the same problem for iOS sign in on iOS < 12.

[tal-mi]

Are you providing "missing-required-fields" include parameter?

[SarahSteininger]

Yes, made no difference.

[tal-mi]

I will take this with our backend team and provide an update when available.

[SarahSteininger]

Thanks!

[tal-mi]

The issue has been moved to our backend team pipeline.
Will continue to update as it progresses into a resolution.