#Error using "node:internal/crypto/sig" module

1 messages · Page 1 of 1 (latest)

near whale
#

Hey guys, I'm trying to use a Google Cloud integration which uses a private key and some sort of cryptographic signing step in their node SDK. I'm getting a failure in my job on step one when I'm trying to instantiate the SDK client. Any advice on how I can fix this? The exact error is:

    at Sign.sign (node:internal/crypto/sig:131:29)```

Thanks
#

I'm assuming this is related to where the code is running, assuming that maybe the edge runtime doesn't have full Node support? Just not sure how to fix that

ocean mural
#

Are you using Next.js? Are you using the edge runtime? By default we aren't on the edge runtime

near whale
#

I am indeed on Next.js but I'm not 100% sure where the code is running, I just did the default setup

ocean mural
#

I think this might be unrelated to Trigger, there's this issue which seems to suggest it's a weird thing with newline character in Google private keys: https://stackoverflow.com/questions/74131595/error-error1e08010cdecoder-routinesunsupported-with-google-auth-library

near whale
#

oh interesting

ocean mural
#

Btw your job code runs wherever you deploy to, e.g. Vercel. And by default in the CLI we create a regular (non-edge) API route at /api/trigger

near whale
#

Ahh ok got it, thank you

near whale
#

That fixed it! Thank you

ocean mural
#

No problem 🥳

near whale
#

Do I mark this complete somehow or just leave it?