You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using googleapis 0.2.13-alpha. I'm having trouble using this module and trying to call the recently released drive.files.watch endpoint. Other endpoints appear to work correctly, but this one is causing the error. The class is correctly discovered, and called using:
user.auth is a valid object containing the clientId, clientSecret, and credentials containing the access_token and refresh_token.
Adding some debugging to BaseRequest.prototype.execute (request.js, after line 125) I can confirm that the authClient has the correct user.auth information. The requestOpts object is set to
It's the RPC backend that causes the problem, the RESTful endpoints are fine. Since, node client is one of the few consumers of the RPC, the severity of the problem is low. I'm planning to fix #8 to get rid of the RPC.
FYI, this method requires you to set a channel parameter instead of setting body. It's inconstent with the rest of the API, therefore I'm pushing the team to fix it. But, for the short term, you can make the calls in the following format:
Using googleapis 0.2.13-alpha. I'm having trouble using this module and trying to call the recently released drive.files.watch endpoint. Other endpoints appear to work correctly, but this one is causing the error. The class is correctly discovered, and called using:
user.auth is a valid object containing the clientId, clientSecret, and credentials containing the access_token and refresh_token.
Adding some debugging to BaseRequest.prototype.execute (request.js, after line 125) I can confirm that the authClient has the correct user.auth information. The requestOpts object is set to
which appears correct. The params field contains
which also appears correct.
The error returned is:
Using the exact same parameters, and the exact same access_token, I have run the following curl command:
Which works correctly.
The text was updated successfully, but these errors were encountered: