You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I call getPaymentUrl in a local shell of firebase functions, it all works. And when I run it in a simple node/express server it also works.
However when I deploy the function to firebase I get this error:
TypeError: Cannot read property 'statusCode' of undefined
at Api.isIdempotencyConflict (/workspace/node_modules/gocardless-nodejs/api/api.js:126:26) at Api.request (/workspace/node_modules/gocardless-nodejs/api/api.js:58:22)
at process._tickCallback (internal/process/next_tick.js:68:7) | more_vert
I think the error being displayed is likely hiding the actual error?
We've just pushed version 1.1.2 to npm, this should show more details about the error rather than the:
TypeError: Cannot read property 'statusCode' of undefined
at Api.isIdempotencyConflict (/workspace/node_modules/gocardless-nodejs/api/api.js:126:26) at Api.request (/workspace/node_modules/gocardless-nodejs/api/api.js:58:22)
at process._tickCallback (internal/process/next_tick.js:68:7) | more_vert
Amazing, so v1.1.2 revealed the actual error in the firebase logs which was that since we're on the free plan firebase was blocking calls to external services. Have now upgraded and works perfectly!
Thanks so much for the quick turnaround and especially @isaacseymour for answering all my questions. Am closing the issue :)
Hi! I'm using firebase cloud functions to host the client and I have this simple boilerplate code set up to add a customer:
When I call
getPaymentUrl
in a local shell of firebase functions, it all works. And when I run it in a simple node/express server it also works.However when I deploy the function to firebase I get this error:
I think the error being displayed is likely hiding the actual error?
Versions:
firebase-functions: 3.6.0
gocardless-nodejs: 1.1.1
node: 10
Thanks, and let me know if you need any more info!
The text was updated successfully, but these errors were encountered: