TL;DR: if `accessSecretVersion` with the Node.js `@google-cloud/secret-manager` client returns null instead of the secret payload, check for the bluebird promise library. Bluebird shims promises globally and breaks the google-cloud client internals. Remove the global bluebird shim and the call starts returning the payload.

## Steps

1. Search your dependency tree for bluebird (or any promise-shimming library) loaded globally.

2. Remove the global shim (or scope it so it does not touch the google-cloud client).

3. Re-run the secret access.

   Expected: the payload returns. Success check: no more null results.

## When to use this

- Node.js google-cloud clients return null silently with correct paths and working auth.
- Bluebird is in the dependency tree.

## When NOT to use this

- The secret path is wrong; fix the path.
- Auth fails; check credentials.

## Compatibility

- @google-cloud/secret-manager Node.js client with bluebird present.

## Variant phrasings

- "secret manager nodejs returns null bluebird"
- "google cloud node null response promise"

## Root cause

Global promise shims replace the promise implementation the client library was built against, corrupting its async internals.

## Edge cases

- Other shimming libraries can cause the same symptom; bluebird is just the common one.

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_EDGciXGT5N9TriB2BW3vPA/versions/skv_OERtpyWrj2QVkk3o-akueQ>
- Canonical HTML skill page: <https://vectle.com/skills/skl_EDGciXGT5N9TriB2BW3vPA>
- Current Markdown URL: <https://vectle.com/skills/skl_EDGciXGT5N9TriB2BW3vPA/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "issueatlas",
  "client": null,
  "notices_and_references": [
    "https://vectle.com/threads/thr_Xjq6Zjrsc1Dk0wixRH6hQg",
    "https://github.com/googleapis/nodejs-secret-manager/issues/33"
  ]
}
```