Start a new topic
Answered

user.save() method overriding social identity

Hi,


Our app has been with Kinvey for 8-9 months now and has the ability to do Facebook login. But for some reason in the last few weeks we have noticed that the user.save() function is deleting the social identity of the User. 


What we are trying to do:

1. Sign up the user with facebook

2. Record their email in the email field in Users. But this does not happen upon creation of the user, so we had to use user.get to get the user, then add the email and then user.save(). This has been working all the time, expect a few weeks ago when we started noticing that the Social identity field is empty.


This is also causing multiple facebook profiles to be created everytime the user logs in.


Can you please help?

Thanks.

Divey


Best Answer

Hello Divey,


We have fixed the Facebook login problem. You can download the latest Kinvey iOS SDK at the following URL.


At your convenience, please download and test the new release to make sure that it fixes the login problem to your satisfaction.

Regards,

Billy Gee

Hi,


Can I please have an update on this? Our app in production is being affected because of this issue.


Thanks.

Divey

Answer

Hello Divey,


We have fixed the Facebook login problem. You can download the latest Kinvey iOS SDK at the following URL.


At your convenience, please download and test the new release to make sure that it fixes the login problem to your satisfaction.

Regards,

Billy Gee
Divey,

We identified an issue where the socialIdentity is not persisted after performing a social login and after that, the update to the server is missing that attributes and does not save them. This is scheduled (as of now) to be fixed in the next sprint and we will keep you posted with the progress on this case. Please accept our apologies for any inconvenience that may have caused.

Thanks,
Pranav
MLIBZ-2169

 

Hi,


Can anyone help with the issue above please?


Thanks.

Divey

Thanks for your response. But can I please request a timeframe for this next sprint? Are we talking weeks or months? This issue is affecting our app in production, which means we will have to remove Facebook sign in until then, and that has huge business impacts on us. Please let me know what best you can do.


Thanks.

Divey

Divey,

I will discuss this internally and get back to you asap.

Thanks,
Pranav

 

Hi Divey, 

I am looking into this issue. I will get back to you with an update shortly.
Could you please confirm which Kinvey SDK are you using? Please mention version too.

Regards,
Abhijeet

Hi Abhijeet,


We are using the Kinvey SDK for iOS and Android. The issue we are having is only with the iOS SDK. The version is Kinvey (3.10.0). We update our pods regularly so would have the latest Kinvey version. Thanks for your help.


Thanks.

Divey

Divey,

Have you added a property for the social identity in the CustomUser class?

 

Thanks,

Pranav

No we have not created a property for the social identity in CustomUser. Like I said our app has been in production for 6-7 months and we have had no issues with Facebook sign up.


What we currently do is:

1. Get the user details and a token using the Facebook sdk.

2. We then pass the token to the Kinvey method >> User.login(authSource: .facebook, faceDict)

3.This creates the user in the Users entity and also creates a social identity.

4. We then manually add the email to the email field but when we press users.save which then adds the email to the email field in Users.


But now, when we add the email, it overwrites the social identity for some reason.


Like I said, this was not happening before so I would like to know if there have been any changes in your system?


Thanks.

Divey

Hi,


Any update on the above please? As said numerous times, this issue is affecting our production app. Can you please provide me with a tentative timeframe for your next sprint release?


Thanks.

Divey

Hi Divey,

Thank you for your quick response, Does this mean it was working for you with Kinvey IOS SDK v3.9.0? If not, Which was the last version for which you had this in working state?

Regards,
Abhijeet

Please see below a timeline of changes for us:

1. Prior to September, we were on version 3.3.9. This was all working.

2. Then we switched over to Xcode 9 and swift 3.2, which then affected majority of our libraries so we had to update our pods. 

3. Once we updated the pods, we would have got the latest version from Kinvey and hence have started noticing this problem from October onwards.


I now tried to go back to the previous Kinvey versions and all still have the user.save() issue. The earliest version I went to was 3.5.1, which does not compile and gives an error for the user.save() which I have attached.


Hopefully this info helps, please let me know if you need anything else.


Thanks.

Divey

Login or Signup to post a comment