Team, I am using monday code secure storage feature to store users acesstoken it works fine in the local environment but throws the below error when deployed to monday code
“Error: some thing went wrong when when communicating with secure storage\n at InternalServerError.BaseError [as constructor] (/workspace/node_modules/@mondaycom/apps-sdk/dist/cjs/errors/apps-sdk-error.js:32:28)\n at new InternalServerError (/workspace/node_modules/@mondaycom/apps-sdk/dist/cjs/errors/apps-sdk-error.js:74:28)\n at validateGcpResponse (/workspace/node_modules/@mondaycom/apps-sdk/dist/cjs/gcp/gcp.js:97:15)\n at /workspace/node_modules/@mondaycom/apps-sdk/dist/cjs/gcp/gcp.js:139:17\n at step (/workspace/node_modules/@mondaycom/apps-sdk/dist/cjs/gcp/gcp.js:33:23)\n at Object.next (/workspace/node_modules/@mondaycom/apps-sdk/dist/cjs/gcp/gcp.js:14:53)\n at fulfilled (/workspace/node_modules/@mondaycom/apps-sdk/dist/cjs/gcp/gcp.js:5:58)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)”
raised a ticket with monday team, but not much traction. Anyone here faced similar issue and has a resolution please help.
I have GCP credentials for my app’s queue for message ordering, as one of the env variables. looks like monday code also uses GCP underneath for it’s Queue and storage implementation(I learnt this from maaps-sdk code from github), so the issue is my GCP credentials has overwritten monday’s credentials so couldn’t able to establish the connection for secure storage.