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/
Related
Whenever a webhook subscription is created for ServiceM8 the previous one is deleted - meaning you can only ever have 1 webhook running at a time.
This happens
When creating a scenario in Make.com(formerly Integromat) using the pre-built trigger modules (which create a webhook automatically).
When creating a webhook via the ServiceM8 API in Postman.com
When creating custom webhooks in Zapier.
If you run an API GET request in the Make.com ServiceM8 module to the ‘webhook_subscriptions’ endpoint then it only ever returns 1 result. (Which is always the last webhook you created in Make.com)
If you then create another webhook in another application (such as Postman) then run a GET request to the ‘webhook_subscriptions’ endpoint, it will only ever return 1 result (the last webhook created in Postman)
Neither application is able to see webhooks created in the other application (even though the GET request should return a list of ALL ‘webhook_subscrptions’
Both of these webhooks will actually now work if you point a separate scenario to each of them in Make.com
But if you create a new webhook in either application, then the old webhook that you had created in that application will stop working.
The only place that you can create and use multiple webhooks from seems to be Zapier.
But even then, it only works if you create the webhooks via the pre-built trigger modules.
If you create any custom webhooks, the same thing happens.
I have tried contacting ServiceM8 support, and their response was;
I understand you came across an issue with our API. I'm afraid we cant provide solutions for the issue here. All information regarding our API is available online through our developer portal you should be able to find any information you need there - https://developer.servicem8.com
You might also be able to find the solutions to your issue on our developer forum (https://developer.servicem8.com/discuss ), or on StackOverflow (https://stackoverflow.com/questions/tagged/servicem8 )
If the solution is not there we recommend that you post the problem in the discussion board on either stack overflow or on our forum the developer community is usually very active and will respond it.
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.
I use this script and I have the following error:
REST API is deprecated for versions v2.1 and higher
Do you know why I'm getting this?
The error says it all. REST API calls are no longer supported by the API in Graph API v2.1. You should get up to date and use the official Facebook SDK to create your Facebook application.
v2.0 is still available until August 7, 2016. So, you can still use the REST API if you like. You are probably getting this because your API calls are either unversioned or they are versioned to v2.1. See this
I have seen discussion in internet about problems (or bugs in Google Drive SDK ) with resumable uploading to google Drive
https://developers.google.com/drive/web/manage-uploads#resumable
and the problem with access_token when it expires after one hour ..
Is there a possibility now ( I understood there should be ) to refresh access token for this ongoing upload ?
I did the test implementation for this but it did not work, when I updated the refreshed access token?
but is this now bug in my code or google drive side ?
If you abandon the library, and simply call the REST API directly, you can implement your own 401 error handling.
edit; see comments below which suggest that the problem is a bug which cannot be circumvented
I recently signed up for a SharePoint Online account. I want to be able to run a local console application and populate a list hosted by my SharePoint online site. How can I do this?
I've tried some code (found here and MSDN info found here) that is supposed to pull list data, but it returns an error "The remote server returned an error: (403) Forbidden." I know the goal is to post data, not pull, but I attempted it as a start.
This site about the Client Object Model contains some additional info about using login information, but it also did not work. There's some discussion in the comments about hijacking a session cookie from Internet Explorer, but this cannot be the best way to approach what should be a simple thing. Lastly, there is a comment on this page that mentions the authentication service is turned off...so I am now wondering if is it possible?
I thought of using the List web service, but I don't know how to get the GUIDs from SharePoint Online.
You need to leverage the claims authentication approach supported by SharePoint Online. Best basic sample of this can be found here: http://code.msdn.microsoft.com/office/Remote-Authentication-in-b7b6f43c/