Repository navigation
pubsub error - Cannot read property 'onAuthorized' of undefined #466
Description
Activity
What version of gcloud are you using? If not master, would you mind testing against that, as we have made significant changes since 0.12.0 was released back in December.
- addedtype: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.api: pubsubIssues related to the Pub/Sub API.Issues related to the Pub/Sub API.
on Mar 26, 2015 i download from github and it's working.
thanks.Phew!
@stephenplusplus I got this error again
Cannot read property 'onAuthorized' of undefined, TypeError: Cannot read property 'onAuthorized' of undefined at onAuthorizedRequest (/home/leibale/workspace/images-processor/node_modules/gcloud/lib/common/util.js:478:19) at /home/leibale/workspace/images-processor/node_modules/gcloud/node_modules/google-service-account/connection.js:56:5 at Connection.<anonymous> (/home/leibale/workspace/images-processor/node_modules/gcloud/node_modules/google-service-account/connection.js:116:5) at processImmediate [as _immediateCallback] (timers.js:354:15)Is there some method you are calling where you aren't specifying a callback?
only
file.createReadStream()andfile.createWriteStream(), but i listen to err and finish eventsOk! If you have a small snippet we could run to reproduce this it would greatly speed up tracking down the bug. That line throwing the error is used by every api request.
i using
file.createWriteStream(),file.createReadStream(),subscription.pull().
i think it's fromsubscription.pull(), but.edit:
please reopen the issueit's happening on
subscription.ack(result.ackId);32 remaining items
- added a commit that references this issue
on Jan 28, 2026 - added a commit that references this issue
on Feb 24, 2026 - added a commit that references this issue
on Feb 25, 2026 - added a commit that references this issue
on Mar 5, 2026 - added a commit that references this issue
on Mar 5, 2026 - added a commit that references this issue
on Mar 12, 2026 - added a commit that references this issue
on Mar 27, 2026 - added a commit that references this issue
on May 5, 2026