我做了这项研究（没有 access_token）：
https://graph.facebook.com/search?q=< /a>"il padrino"&type=page&fields=id,name
在结果中我看到第一个：
"id": "104130852958000",
"name": "Il padrino"
这是“il padrino”最重要的页面，您可以在 Facebook 上手动搜索时看到。
然后我做了这项研究（使用带有每个权限的 access_token）：
https://graph.facebook.com/search?q=%22il%20padrino%22&type=page&fields=id,name&access_token=ACCESS_TOKEN
在结果中有人消失了，而且之前的ID：104130852958000！！！
我用与“il padrino”不同的其他字符串尝试了这种奇怪的行为，但在许多情况下存在相同的问题（反之亦然：一些结果在没有 access_token 的情况下消失）。
怎么可能呢？我如何获得完整的结果列表？
实际上我认为我必须在有或没有access_token的情况下加入研究......但这看起来很奇怪。
I did this research (without access_token):
https://graph.facebook.com/search?q="il padrino"&type=page&fields=id,name
Among results I see the first one:
"id": "104130852958000",
"name": "Il padrino"
which is the most important page for "il padrino", as you can see when you search manually on Facebook.
Then I did this research (with an access_token with every permission):
https://graph.facebook.com/search?q=%22il%20padrino%22&type=page&fields=id,name&access_token=ACCESS_TOKEN
Among results someone disappeared and also the one before with id:104130852958000!!!
I tried this strange behavior with other strings different from "il padrino", but in many cases there is the same problem (or viceversa: some results disappear without the access_token).
How is it possible? How can I get a complete list of results?
Actually I think I have to join the research with and without access_token... but it seems strange.
发布评论
评论（2）
这很烦人。请将其记录为 Facebook 的错误：https://developers.facebook.com/bugs 并发布也链接到您的报告，以便其他找到您问题的人可以看到它的当前错误。
That's annoying. Please log it as a bug with Facebook: https://developers.facebook.com/bugs and post a link to your report here too so others who find your question can see it's current bug.
不，这是不可能的。您不能依赖返回的内容，因为它可能并且很可能会返回。尝试预测搜索结果是错误的，结果可能（而且确实）因用户、地理位置、内容限制以及可能的其他因素而异。
顺便说一句，无论是否使用
access_token，我都没有收到您所说的页面。No, this isn't possible. You cannot rely on what is being returned since it may and probably will. Trying to predict search results is just wrong, the results may (and really do) differ between users, geographical locations, content restrictions and probably other things too.
BTW, I'm not getting the page you speak about no matter using
access_tokenor not.