-
Notifications
You must be signed in to change notification settings - Fork 253
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Validation failed #117
Comments
Also, you should update; The 0.7.x are obsolete and the Thuzi repo is unmaintained. |
I have added appId and Secret on the client side. |
Stack trace: { [ValidationError: User validation failed] |
I'm not asking about client side, Facebook's official client SDK has nothing to do with this node API library, configuring Facebook's SDK will not configure this library. You have to configure appId and the secret with You also should not be configuring your app secret client side, that is a security issue. Additionally, that is not a stack trace. Stack traces have filenames and line numbers for the call stack at the point where the error was generated. |
Receiving validation failed at:
FB.setAccessToken(accessToken);
FB.api('/me', function (data) {
if (data && data.error) {
if (data.error.code === 'TIMEDOUT') {
return Errors.errorCustom(res, 'FACEBOOK TOKEN TIMEOUT');
} else {
return Errors.errorCustom(res, data.error);
}
} else {
});
}
Error: { [ValidationError: User validation
message: 'User validation failed',
name: 'ValidationError',
errors:
{ name:
{ [ValidatorError: Path
name
message: 'Path
name
is reqname: 'ValidatorError',
properties: [Object],
kind: 'required',
path: 'name',
value: undefined } } }
{ [ValidationError: User validation
message: 'User validation failed',
name: 'ValidationError',
errors:
{ name:
{ [ValidatorError: Path
name
message: 'Path
name
is reqname: 'ValidatorError',
properties: [Object],
kind: 'required',
path: 'name',
value: undefined } } }
Even though /me API is working fine at the client side. Any specify reason why I am receiving validation failed?
The text was updated successfully, but these errors were encountered: