Currently it looks like the lice SDK returns error 500 for all request. Also the interactive SDK Microsoft provides here returns the same error:
http://isdk.dev.live.com/dev/isdk/ISDK.aspx?category=scenarioGroup_core_concepts&index=1
My application work without any changes for over 24 months. Has someone any more details or a workaround?
Update: I tried the following API calls both with the same result:
https://apis.live.net/v5.0/me?access_token=#Token#
https://apis.live.net/v5.0/me/picture?access_token=#Token#
Finally, and after a very long downtime (more than 20 hours) the Live API is up & running again.
Unfortunately, there is not even an official announcement from Microsoft.
Up & Running
Have the same problem and all of my apps worked before for very long time.
I'm using LiveSDK 5.6 and getting successful response for LiveAuthClient.LoginAsync with the following scopes: "wl.signin", "wl.basic", "wl.contacts_photos", "wl.contacts_skydrive",
"wl.skydrive_update"
LoginAsync returns LiveLoginResult object where:
Status = Connected
Session = {Microsoft.Live.LiveConnectSession} with AccessToken
but when app trying to call
Session (LiveConnectClient) object with GetAsync ("/me")
I'm getting the following exception
[Microsoft.Live.LiveConnectException] = {"An error occurred while retrieving the resource. Try again later."}
ErrorCode = "server_internal_error"
The OneDrive service experienced a service outage on the 9th, you can see from this 3rd party site for an idea of the timeline. We did not communicate this issue well to you and other developers that have come to expect excellence from OneDrive.
It is the start of a long weekend and I do not have more answers for you at this time, I'll circle back next week with better details on what to do in the future.
The Live Connect API that the LiveSDK works in conjunction with has been replaced by the OneDrive API, which also has SDKs for most major platforms. You will see major performance improvements and a larger feature set such as a modern sync API available for you with this new API if you transition to it.
Related
I use the youtube bulk reports (youtube analytics and reporting api) and get few of the reports on a daily basis , by first listing the reports available for the jobs I have defined and then downloading. The API call made to list the reports available "https://youtubereporting.googleapis.com/v1/jobs/{jobId}/reports" is consistently giving 500, Internal error for the whole day ( 5/14/2017) , where as the query to list jobs does give the required list of jobs (https://youtubereporting.googleapis.com/v1/jobs). I have tried this from my code which has been working for past several months as well as from the Oath Playground tool.
Questions
(a) How does one get more information when this happens, the error in documentation just asks to try later
(b) Is there a place we can see the status of youtube-analytics-api health, so that we know there is a production issue , if any
My company is using zend gdata 1.11.7, relatively old, but they havent had the ability to move to newer things yet. We have a program that adds events to a google calendar based on the forms submitted by the user.
This morning, we now get the error below:
Fatal error: Uncaught exception 'Zend_Gdata_App_HttpException' with
message 'Expected response code 200, got 403< HTML>< HEAD><
TITLE>Forbidden< /HEAD>< BODY BGCOLOR="#FFFFFF"
TEXT="#000000">< H1>Forbidden< H2>Error 403< /BODY>< /HTML>
' in
/homepages/26/d119734641/htdocs/app/ZendGdata-1.11.7/ZendGdata-1.11.7/library/Zend/Gdata/App.php:709
From everything I am reading, this is an authentication issue...but I have a problem, it was built so long ago that we do not have access to the google console for the API, what else could be the problem? Did google stop supporting this way of authenticating that is used in this zend gdata?
Please help as currently I have everything happening manually from our online database to the calendar.
Found this post
Zend google Calendar access not working anymore
Seems they discontinued it....
Back in November 2011, we announced the deprecation of the Calendar GData API (v1, v2) when the APIv3 was made available. We’ll now be shutting down these older versions on November 17, 2014.
https://developers.google.com/api-client-library/php/
seems to be the way to go. Still working on replacing my Zend_GData (Zend V1 project) with this but it seems promissing.
EDIT
I can confirm i was able to migrate all my zend_Gdata to google-api-php-client-master.
I can create event, update event, delete event, i work also with extendedProperties, all is fine. I've just one concern about the OAuth and the refreshToken, i hope that i understood how it work.
/EDIT
You can't use Zend anymore to list, add, delete events. You have to use google api v3. Here is an example of class you can use to manage events: Authentification Zend Gdata (403 forbidden)
I am mining some tweets from twitter via twitter 4j. My code is running on a server and until yesterday I had no issues however I have recently started to get this error.
403:The request is understood, but it has been refused. An accompanyll explain why. This code is used when requests are being denied (https://support.twitter.com/articles/15364-about-twitter-limits-updatng). message - Missing or invalid url parameter. code - 195
When I run the same code locally I cannot reproduce this error and I am allowed to mine tweets just fine. Furthermore I am confident that I am working within Twitter's rate limits and all I am accessing is tweets. I am not updating anything in my code. Finally, when I wait until the reset time and run the code on my server again, the same error occurs without allowing me to mine any tweets.
I have looked online and cannot find a solution to this problem. Has anybody encountered something similar? Please help.
Suddenly simple Facebook Graph API calls started to return an empty result. The node I'm calling is a simple search page by name:
`https://graph.facebook.com/search?type=page&fields=profile_picture,username,id,name,likes,category,talking_about_count&access_token=<APP_TOKEN>&limit=10&q=stackoverflow`
It just started to return an empty result set when called from my server:
{"data":[]}
When I'm calling it from my personal computer browser, it works just fine.
I don't see any notification in Facebook Manage Apps page. What can be the reason? Is there any way I can see any error in this Graph API result?
UPDATE: suddenly it started working again, after it was down for at least 2 hours. Is there any way I can make these calls through client side JS? Any way to avoid to exposure of my APP_TOKEN?
UPDATE2: It stopped working again, and although I haven't identified the reason, I did figure when replacing the with a , it does work. The documentation actually says to use an APP_TOKEN.
Well i started of by following all the instructions here:
http://code.google.com/p/xmppframework/wiki/FacebookChatHowTo
I used the recommended fork of the facebook api and tried the latest from:
https://github.com/facebook/facebook-ios-sdk/
My problem starts with the following error:
< failure xmlns="urn:ietf:params:xml:ns:xmpp-sasl">< not-authorized/></failure>
The error is a reply from facebook to xmppframework s response to a authentication challenge. The response that is made by the iphone is base64 encoded msg when i decode it i find 2 of the values are null:
api_key=(null)
and the
session_key=(null)
This is obviously the reason facebook is returning that error. But the problem i have is i cant seem to find any where to set these values in the framework. Besides i think the session_key should be pulled in from facebook anyway.
I guess what i want to know is a couple of things.
Has any one got the xmppframework working with facebook on a iDevice?
If you have got it working did you have to stray from the path of the instructions on http://code.google.com/p/xmppframework/wiki/FacebookChatHowTo ?
do you know of any other method to get facebook chat working on the iphone?
Any suggestions or help for my current dilemma would be appreciated. Happy to share my code if you want.
cheers
I wrote the Facebook integration for XMPPFramework. The api_key and session_key, come from a call to auth.PromoteSession. Facebook is trying to deprecate that call, so to enable it, you must follow step 7, in the HowTo:
Under Migrations, change Disable Deprecated Auth Methods from Enabled to Disabled and Save Changes.