Closed dtsehl closed 10 months ago
+1
Same issue, fixed by downgrading to v17.0.2 so most probably introduced by this commit.
@stcheng Would you be able to have a look at it?
will take a look. if no short term feasible solutions, i would probably do a git revert on this specific commit. thanks for reporting this.
You should debug "constructErrorResponse" method and see what fields axios response returns. You return undefined because you do not construct from the correct fields on version 18.0.1.
@stcheng have you had a chance to debug this one yet?
working on a fix; will update soon.
Thanks!
anyone please help verify if this issue has been properly addressed and if that is the case i'll tag a new version thank you all
closing this as addressed in v18.0.2.
Sorry for the late reply. I am able to confirm that the fix worked on v18.0.2. Thank you :)
@krishna-koushik no worries. thanks for confirming this.
Hey @stcheng thanks for the fix, but why wasn't this backported to v17 given it's still in the support period?
Which SDK version are you using?
17.0.3
What's the issue?
We are not receiving any error codes, specific errors or anything similar when calling various endpoints, so we cannot debug what an error might be when we send a call. We are only receiving a generic FacebookRequestError.
Steps/Sample code to reproduce the issue
Observed Results:
We are receiving this error response back when making the call:
Expected Results:
We expect a more verbose error back other than a generic FacebookRequestError, so that we can debug what the issue is.
For example: