google-api-dotnet-client: 404 on every call through BatchRequest
I get 404 (“Response status code does not indicate success: 404 (Not Found).”) on every call through BatchRequest.
What I mean, before I used BatchRequest and didn’t specify custom batchUri:
var batch = new BatchRequest(service);
Since https://developers.googleblog.com/2018/03/discontinuing-support-for-json-rpc-and.html I tried to use custom uri for each services. For eaxample for Youtube data API:
var batchRequest = new BatchRequest(service, "https://www.googleapis.com/batch/youtube/v3");
But on every call I heav got an error.
What I do incorrectly or it doesn’t work at all ?
Thanks.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 2
- Comments: 24 (15 by maintainers)
The API team has confirmed (with 100% certainty) that the fix is fully rolled out. I’ve been running my test code and @alenvall’s all morning and I haven’t seen any errors. I’ll leave this open until I hear from some of you, but this time this really should be working.
This is still being looked at by the API team. As soon as it is working I’ll update here.
A fix is being tested and should start rolling out to prod after. As soon as I confirmed is out and working I’ll update here.
Any update on this? It’s preventing us from fetching data required for business needs.
This is being looked at internally. In the meantime, the only workaround is that you switch to making individual requests where possible. I’ll keep updating here as I know more.
I’ll look at this tomorrow UK time.
Assigning to Amanda to look at when we return to work, but please be aware that Monday is a public holiday in the UK, so we probably won’t get to this until Tuesday.
@alenvall Actually I just ran into a 501 a few times trying to reproduce with your code and with mine as well. But it worked well some other times. Might just be that it really hasn’t fully rolled out even though I got confirmation. I’ll report internally and I’ll also try to reroute this issue directly to the API team so I’m not in the middle anymore, it is a waste of time for everyone. This is definetely not a library issue, but an API issue, and it seems not to be fully resolved.
I’ll reopen this one until I have rerouted though so feel free to leave your comments here with other findings.