Start a new topic

Social identity connect methods missing from User?

According to the v3 migration guide, the guide on users and the User API docs, there should be a connectFacebook() static method on Kinvey.User for handling sign-in via facebook. That method, and the other similar methods for other social platforms, are missing.

I followed the oauth tutorial and set up a Google provider in case the functionality I'm looking for is dependant on having an entry in the oauth collection, but that didn't add a connectGoogle() method to User (or make the connectFacebook() method show up).

What am I doing wrong?

I'm using the HTML5 dev kit, kinvey-html5-sdk@3.10.0 installed with npm. 


Can you please try using "connectIdentity()" method for Social identity login as mentioned on the following link and let me know if it solves your problem?



I'd try that, but I'm not sure what to pass for the 'session' parameter (maybe the accessToken field of the Facebook authResponse. I did find the following elsewhere on the forums, though it seems really hacky so if I can get connectIdentity to work I'll probably switch to that:



        _socialIdentity: {

          facebook: {

            access_token: authResponse.accessToken,

            expires_in: authResponse.expiresIn,




          user => ...



Hi Laurie,

Please use the Kinvey.User.connectIdentity() method as shown here by passing the access token from the Facebook authResponse. The other methods are deprecated and will be removed from the documentation.

The method you have found is correct - it is actually the object that the the SDK is passing internally through the method above. More information about it can be found in the REST API documentation.

Let me know if this has helped.

Martin, thanks, that definitely helps -- now I know that my solution is valid, as well as how to correctly use the proper API to achieve the same result. 

Please consider:

  • marking deprecated APIs as such in the documentation
  • retaining support for deprecated APIs as long as they're still documented
  • updating documentation that references deprecated APIs to describe the preferred alternative approach
I know that documentation is always in flux but there's nothing worse than reference documentation that's incorrect when trying to learn a new platform.

Login or Signup to post a comment