google-ads-api: assets.get method throw `Error: no such type: google.ads.googleads.v8.errors.GoogleAdsFailure`

Hey,

Im using version 8.0.1 of this package, and encounter with a new error/behaviour: i ran this code several times, the exact same code, with the exact same input: (the ids been removed for obvious reason)

await customer.assets.get('customers/<CUSTOMER_ID>/assets/<ASSET_ID>');

and half of the times i get the following error:

/Users/user/dev/project-service/node_modules/protobufjs/src/namespace.js:383
        throw Error("no such type: " + path);
              ^
Error: no such type: google.ads.googleads.v8.errors.GoogleAdsFailure
    at Root.lookupType (/Users/user/dev/project-service/node_modules/protobufjs/src/namespace.js:383:15)
    at GoogleErrorDecoder.decodeProtobufAny (/Users/user/dev/project-service/node_modules/google-gax/src/googleError.ts:67:28)
    at /Users/user/dev/project-service/node_modules/google-gax/src/googleError.ts:112:14
    at Array.map (<anonymous>)
    at /Users/user/dev/project-service/node_modules/google-gax/src/googleError.ts:111:57
    at Array.forEach (<anonymous>)
    at GoogleErrorDecoder.decodeRpcStatusDetails (/Users/user/dev/project-service/node_modules/google-gax/src/googleError.ts:106:15)
    at Immediate.callback (/Users/user/dev/project-service/node_modules/google-gax/src/call.ts:123:39)
    at processImmediate (node:internal/timers:466:21)
    at process.topLevelDomainCallback (node:domain:147:15)
    at process.callbackTrampoline (node:internal/async_hooks:128:24)

Even when i try to wrap this piece of code with try/catch block - it doesn’t seems to help, and my entire process crash.

reverting back to version 5.2.0 didn’t helped.

Please advise.

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 16 (2 by maintainers)

Most upvoted comments

This should be fixed in a google-gax dependency (in v2.22.0) that was just released, so please reinstall the dependencies and make sure npm ls google-gax shows 2.22.0 or newer.

@arditti have you done anything related to it?

Sadly we didn’t find any workaround yet. we are looking for any clue in order to solve it.

will keep this thread updated on any findings.

We are facing serious issues of restarts of the node app on GAE due to this issue. can anyone suggest temporary workaround for it?

Happens on other method as well, like getting reports for ad_group_ad resources. Im pretty afraid that try/catch does catch these errors

@arditti @WillCooter I am also facing this issue since 3 to 4 hours and checking for the solution. I have raised same error here

https://github.com/Opteo/google-ads-api/issues/308

can you please update us on it?