Hello Luciano,

thanks for your answer. As you suggested I've upgraded my local 
dev_appserver version to 1.9.34.

*GraphMethodException* is related to a search that cannot be served by the 
Graph API since there is no handler for it. I don't think this is the case 
since, as mentioned, I can access the same url I query from the GAE 
instance, using CURL and in that case I obtain a valid result and not an 
exception. 
It works also on my local instance, when I use the interactive console and 
use urlfetch.fetch. It also works when I fetch the sm API url from inside 
my program on my local machine.

Summarizing:
- from terminal: 
curl 
"https://graph.facebook.com/v2.3/184277601936688?access_token=xxxxxxxxxxx"; 
*WORKS*

- from local instance:
from google.appengine.api import urlfetch


u = urlfetch.fetch(
"https://graph.facebook.com/v2.3/184277601936688?access_token=xxxxxxxxxxx";)
print u.content
*WORKS*

*- *from local instance program runs and visits API endpoint: *WORKS*

- from GAE remote instance
from google.appengine.api import urlfetch

u = urlfetch.fetch(
"https://graph.facebook.com/v2.3/184277601936688?access_token=xxxxxxxxx";)

print u.content
*DOES NOT WORK*

*- *from remote instance program runs and visits API endpoint: *DOES NOT 
WORK* 

At the present time, I cannot find the problem. I thought it could be that 
facebook just cut off requests coming from GAE or certain ips... but it 
does NOT happen for all the facebook ids I try to query, only for some of 
them.


On Thursday, March 17, 2016 at 10:09:26 PM UTC-7, Luciano Pacheco wrote:
>
> Hello Diego,
>
> I'm Luciano from Google Cloud Support.
>
> The issue mentioned on the email you that received yesterday has been 
> fixed. So the error you're experiencing is unrelated.
>
> I searched online for "facebook graphapi GraphMethodException" and it 
> seems related to some permissions on the Facebook app or entity being 
> updated, see this stackoverflow question 
> <http://stackoverflow.com/questions/17209975/facebook-open-graph-graphmethodexception-error-code-100>
>  for 
> example.
>
> I also suggest you to upgrade your local environment from 1.9.20 to our 
> latest version 1.9.34 <https://cloud.google.com/appengine/downloads>.
>
> Cheers,
>
> Luciano Pacheco
>
> On Friday, March 18, 2016 at 5:26:13 AM UTC+11, Diego Marchi wrote:
>>
>>
>> urlfetch.fetch is reporting inconsistent results when querying the 
>> facebook graph api. If I curl the same URL from my terminal, it works fine. 
>> It works ok also using the local instance of the GAE with dev_appserver.py.
>>
>> I am using a mac and the dev_appserver version on my local is 1.9.20. I 
>> am using Python.
>>
>> I cannot share the access token, but the url I am trying to reach is "
>> https://graph.facebook.com/v2.3/184277601936688"; - from the remote 
>> instance I saw the logs reporting this:
>> {
>>    "error": {
>>       "message": "Unsupported get request. Please read the Graph API 
>> documentation at https://developers.facebook.com/docs/graph-api";,
>>       "type": "GraphMethodException",
>>       "code": 100,
>>       "fbtrace_id": "He4bs+MI7Qs"
>>    }
>> }
>>
>> but with curl and also on my local instance, I get a proper response and 
>> a JSON document.
>>
>> anybody has any advice on this? I received an email yesterday from 
>> google, stating that url_fetch has some inconsistend behaviour and I 
>> believe I stumbled in it. They say to contact their support in this case 
>> but where can I reach them?
>>
>> Thanks
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b5887a02-b09b-4f44-81e1-48b45e768800%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to