Cannot fetch any secrets

[Jeremy-Magical]

Scenario & Reproduction Steps

I'm using client.secrets.resolve to try to resolve a secret reference that works on the CLI but I keep getting:

(v0.1.6)

error error resolving secret reference: unable to fetch vault attributes error when retrieving all vaults metadata: http error: error issuing the request with reqwest: error sending request: promise resolved to unexpected type

(v0.2.0)

error Error: error resolving secret reference: unable to retrieve vaults: request library compatibility issue, check that the your environment uses compatible versions: reqwest library: error sending request

When I try to use the client.items.get I get this error
(v0.2.0)

 Error: request library compatibility issue, check that the your environment uses compatible versions: reqwest library: error sending request

Actual Behavior

I cannot make any API requests it seems

Expected Behavior

No response

SDK version

v0.2.0

Additional information

• Again I tried using the same service account key with the CLI and everything worked fine.
• I confirmed the auth token is set properly

[MOmarMiraj]

Hello @Jeremy-Magical ,

This error could arise due to an unsupported NodeJS version. We support NodeJS v18 above and I see that this hasn't been documented anywhere. I will create a ticket to document this correctly

[Jeremy-Magical]

Hello @MOmarMiraj !

I am on nodeJS v22.13.0

[parkersm1th-magical]

Hi @MOmarMiraj,

I am also on node 22 and am experiencing the same bug.

[MOmarMiraj]

Hey,

Hmm I see, I have a couple of questions:

1. Does it only happen with secret references? and Items.Get or is it every SDK call?
2. Is it only that specific item or is it all items?
3. Have you tried other SDKs with the same service account token and do you get the same error?

and any information you think is necessary you could also drop here and I can investigate it for you folks!

[Jeremy-Magical]

1. its every SDK call
2. All items
3. I have tried this service account with the CLI and I am currently using https://github.com/1Password/op-js as a workaround

[MOmarMiraj]

I see, I can look into this more but I need your details. Can you please send your account name / domain (.com/.ca/.eu) / UUID to support@1password.com, referencing this GitHub thread? I'll be able to pick it up from there and look for more information in the server logs.

Also once you submit, could you also share your Ticket ID with me? Would need it to find the email.

[Jeremy-Magical]

@MOmarMiraj Thank you! I've send over the information. Ticket Number: TYY-58836-126

[MOmarMiraj]

Hi @Jeremy-Magical,

Thank you for your ticket and I received it, I couldn't find anything unexpected around about your issue. All the API calls to have succeeded on our end so I have a couple of more questions for yourself.

1. Are you running the SDKs through a proxy?
2. What OS and OS version are you on?
3. Is this issue reproducible or is it sporadically happening?

And just to be safe, can you try it with the latest SDK v0.2.1 and does it also happen on the latest?

[MOmarMiraj]

Hi @Jeremy-Magical

Just wanted to follow up if this is still an issue or it has been fixed?

[matthew-magical]

Jeremy isn't available right now so answering for him

• Are you running the SDKs through a proxy?

No

• What OS and OS version are you on?

macOS Sequoia

• Is this issue reproducible or is it sporadically happening?

IIUC it was reproducible every time

Just wanted to follow up if this is still an issue or it has been fixed?

We have a workaround using the CLI instead of the SDK so I can't say for sure.

[MOmarMiraj]

Thanks @matthew-magical ,

Could you folks try running the example file we have (.cjs or .mjs doesn't matter) and see if you get the same issue. If this works, I am assuming theres something in your code that you import that might be interfering with the SDKs.