Cloud code unable to reference Facebook auth data

[antonfire]

Check out #1271 for an ideal bug report. The closer your issue report is to that one, the more likely we are to be able to help, and the more likely we will be to fix the issue quickly!

Many members of the community use Stack Overflow and Server Fault to ask questions. Read through the existing questions or ask your own!

• Stack Overflow: http://stackoverflow.com/questions/tagged/parse.com
• Server Fault: https://serverfault.com/tags/parse

For database migration help, please file a bug report at https://parse.com/help#report

Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!

• [ y] You've met the prerequisites: https://github.com/ParsePlatform/parse-server/wiki/Parse-Server-Guide#prerequisites.
• [ y] You're running the latest version of Parse Server: https://github.com/ParsePlatform/parse-server/releases
• [ y] You've searched through existing issues: https://github.com/ParsePlatform/Parse-Server/issues?utf8=%E2%9C%93&q=is%3Aissue Chances are that your issue has been reported or resolved before.

Environment Setup

• Server: 2.2.10, node running on ASW Elastic Beanstalk
• Database: Mlab

Steps to reproduce

When running cloud code in parse server 2.1.6 everything works fine, upon upgrade to 2.2.10 when referencing the Facebook user id held in authdata I get an authdata undefined error. I had similar issues when I attempted to upgrade to 2.2.7, see > #1579.

I am referencing authdata in the cloud function as follows:

var currentUserFacebookID = request.user.attributes.authData.facebook.id;

As noted above this works in v2.1.6.

Logs/Trace

Elastic beanstalk logs this as:

[31merror�[39m: Uncaught internal server error. [TypeError: Cannot read property 'facebook' of undefined] TypeError: Cannot read property 'facebook' of undefined
at /var/app/current/cloud/main.js:1149:74

[steven-supersolid]

Does this work in 2.2.8?
The bug in 2.2.7 was that a queried for user would not contain authData.
Your issue may be that request.user does not contain the attributes. There are a number of tickets about this, with some feedback in #1836

If it is the latter then one workaround is to do a fetch/query on request.user

[antonfire]

No I tried 2.2.8 and the situation is the same.

[antonfire]

I resolved this by wrapping my code for each cloud function in the following:

    var userAuthQuery = new Parse.Query(Parse.User);
    userAuthQuery.equalTo("username", request.user.attributes.username);
    userAuthQuery.first({useMasterKey: true,
      success: function(authDataObject) {

                 // to access authdata do this...

                var currentUserFacebookID = request.user.attributes.authData.facebook.id;

              // old code goes in here

    }, function(error) {
         response.error("get authdata info lookup failed");
    }});

[steven-supersolid]

I've been on vacation so only just getting back to this. That is similar to what we do. I think you should be fine as username is unique. We query on request.user.id as that doesn't rely on attributes.

It's strange that the username attribute is present but not the authData so definitely something wrong there.

[miracle7]

@antonfire just fyi, @flovilmart has made a promising pull request (#2348) to finally resolve this issue, so you may be able to take out your workaround (which doesn't work for me unfortunately) in the next version if the PR makes it in. Hopefully it gets merged soon.