I've just noticed that this method is failing in my ASP.NET web application because I'm not catering for 'expires_in' being missing in the response.
I haven't changed any code recently, and was not aware of any reason for this to be missing in the response. Does this mean that the token has expired?
I'm using version 7.0.6 of the C# Facebook SDK and v2.5 of the Facebook Graph API.
The JSON response looks like this:
{"access_token":"xxxx","token_type":"bearer"}
There is an open bug report about this on Facebook's bug tracker. Given Facebook's response it does indeed sound like it's a bug on their end, and appeared some time yesterday.
Updates will appear in that bug report, and you can subscribe to it to give it more visibility and to receive updates.
Thanks to CBroe for pointing out the bug report in his comment on the question.
Related
enter image description here
When trying to subscribe from below URL, it keeps failing due to too many redirects.
https://api-portal.videoindexer.ai/products/authorization
The site is undergoing an upgrade. See my earlier question here.
Patience is the only answer now.
Video Indexer api-portal should be fully available for you from now on.
Video Indexer team.
I've been successfully pulling messages from my pages using the Facebook Graph API until today when I started getting an error:
GraphAPIError: (#12) This endpoint is deprecated for versions v2.4 and higher
I double checked my permissions using the Graph API Explorer tool, and replicated the error there:
I also double checked the Conversation Facebook Graph API reference, and it says
GET graph.facebook.com/{id}?fields=messages{message}
should work to access the content of a specific conversation, however I keep getting the deprecation error any time I'm trying to access to messages field.
Any thoughts what could have broken since yesterday, or an alternative way to extract my page messages trough the Graph API?
This is a Facebook bug that's being treated as high priority.
Hopefully they'll fix it soon.
https://developers.facebook.com/bugs/163782704230317/
Not sure what is I missing here. No analytics graph showing up
Are you using Analytics?
If not, try to disable it and try again.
I was having similar issue, i haven't setup xDB for Analytics.
So, it was giving me error while getting Tracking information.
I am trying to connect to a newly created Google spreadsheet, using the WSO2 Data Services Server (DSS), but it keeps giving me an error when I test the connection. I am using WSO2 DSS 3.2.1 with JDK 1.7.0_60 on Windows.
The sample Google spreadsheet is working fine.
It looks like this problem is due to the new format of the Google Doc URLs (introduced in March 2014)
https://docs.google.com/a/ishafoundation.org/spreadsheets/d/1U0uI5sKHy0WVgQcVtZ4mYMHSzTYZZJse35xy1Y1N7Xg/edit#gid=0
The older format is:
https://docs.google.com/a/ishafoundation.org/spreadsheet/ccc?key=1U0uI5sKHy0WVgQcVtZ4mYMHSzTYZZJse35xy1Y1N7Xg&usp=drive_web#gid=0
As a workaround to this, I am creating my spreadsheet in the old version of Google Sheets, using this link:
https://g.co/oldsheets
However, this message is on the Google Sheets help page
*Spreadsheets created in the old version of Sheets will eventually be converted to the new Sheets, which won’t require any action on your
part. More details coming soon. Thanks
This looks a bit scary to me, since it basically means that my data service will break at some random point in the future when Google decide to change the URL formats... Can someone from WSO2 let me know if this will be fixed in the next DSS update, and when we can expect it to be released.
Just a suggestion - but wouldn't it be better if we only had to enter the unique key for the spreadsheet (instead of the full link), and the DSS server used the Google Sheets API to retrieve the data. This might make our implementations a little more future-proof.
Yes this will be fixed in DSS 3.2.2 release. Associated JIRA is DS-930. Alpha pack can be found from this location
Thanks
Chanika
The presentation today indicated that there was support on Stackoverflow but I was wondering if there's a central location where all requests are being tracked for us to follow and vote on?
If you have a very specific request for the Glass Development Kit, the best place to file it is in the Glass API issue tracker. There's a Component-GDK tag being used for these requests.
In general, though, not much has been said about the GDK yet, so it may be a bit early to make specific issue requests until more context is available.
For now, if you're a member of the Explorer Program, the Glass Pioneers section of the Glass Community is a great place to discuss your thoughts on the GDK.
There's a "request new API Features" link on the Glass API issue tracker page, but it's not clear if that is the best place for GDK feature requests since a lot of the branding on the page lists it as the Google Mirror API issue tracker. There seem to be a few GDK-ish feature requests in that issue tracker though, so in the absence of any official information I'd probably submit them there.