after few moonths using youtube reporting api from a C# console app to download reports as content manager, today I am receiving code 500 error (Internal error). Nothing has changed in the relevant code, and everything always went smoothly before. I am receiving the same error in Google API's Explorer.
The YouTube API Reporting service was out of service. I just have to wait for a few hours and everything was working fine again
Related
I have weird problem with YouTube Api V3.
My app is on AngularJS and it works perfectly. The only one problem is when I try to subscribe for a channel, I receive 500 Internal Server Error. The interesting thing is that I receive this error only on iOS. When I use the app on Android I receive 200 OK and the user is subscribed for the channel. When I try through Postman it also works as it is expected but I can't understand what's the problem with iOS.
Аny ideas where the problem might be?
I am using LinkedIn authentication to log in into my iOS app. It was working fine until few days back. It suddenly stopped working without any changes in the code.
When a user tries to log in via oauth, it just fails with the error message - Domain=LIALinkedInERROR Code=2 and no localised description. However, authentication via LinkedIn app works. I've tried searching on the internet for similar issue but couldn't find anything related. I have also tried it on other apps on play store and its the same with those apps too. Has LinkedIn changed the API's or something?
My application using YouTube api gives me this error response when this is on google app engine
<?xml version='1.0' encoding='UTF-8'?><errors><error><domain>yt:quota</domain><code>too_many_recent_calls</code></error></errors>
But on localhost everything works fine.
This application is in sandbox mode so, hardly any request going to YouTube from the Google App Engine server.
Frequently i am getting this error.
please help me.
Do you use your personal API key? If not, start doing so, otherwise your allowed quotas will be very small. If you have your API key, you will be able to check your quota usage in your developer console—and you will be able to check why your quota is exceeded.
Source: https://developers.google.com/youtube/faq#quota, https://developers.google.com/youtube/v3/getting-started#quota
After running smoothly for an entire year, a 'create' call to the Google Documents List API started giving 403 Forbidden errors.
Other methods work fine with the same access_token parameter. This started around December 7th very consistently across all of our users invoking this call.
This API just recently got a deprecation policy where it will stay intact until April 2015. To be fair, I don't expect the Google Drive team to be actively supporting this API, but wondering if there is a chance that something on the Google Drive transition could be related to this inconsistency.
Is anyone else experiencing unexpected errors on the Google Documents List API? Any clues as to what is going on, and how deep might the issue be?
Thank you!
as of about 3 hours ago every call to the Doclist API using 2-legged OAuth started failing with "500 Internal Error" messages.
We have verified this from multiple systems (App Engine and local apps) using different libraries, and across domains in Asia, US and Europe.
The problem does NOT occur if normal user authentication is used - only 2LO is affected.
Unfortunately this issue affects thousands of students using our tools.
http://code.google.com/a/google.com/p/apps-api-issues/issues/detail?id=3233&thanks=3233&ts=1347419864
Jan
This is tracked at http://code.google.com/a/google.com/p/apps-api-issues/issues/detail?id=3233 and the fix should be live very soon.
UPDATE: everything is now back to normal