Geek Answers Handbook

Are non-user photos still available on Facebook Open Graph v2.0?

In Graph API v1.0, I could get a profile image of any user with the following call to graph.facebook.com/{uidasket/picture ( fb doc ).

In Graph API v2.0, facebook says it will return (a) application user identifiers for applications for users and (b) temporary tokens for users without an application (via / me / taggable_friends and / me / invitable _friends api calls). Based on this, I would suggest that calling the api image is not recommended in version 2.0. However, in the documentation, it looks like this call was not changed in version 2.0.

Does anyone know if publicly available photos of non-application users will be available (in full size) in version 2.0?

+3
facebook facebook-graph-api facebook-opengraph
source share
3 answers

You can still get the profile picture of a person in version 2.0.

http://graph.facebook.com/v2.0/APP_SCOPED_ID/picture will be redirected to the image of the user represented by this application area identifier.

If a user previously registered in your application when your application was encoded against v1.0, they can still be known to your application by their original Facebook user ID. For this reason, http://graph.facebook.com/v2.0/ORIGINAL_USER_ID/picture will also work.

+6
source share

/<user id>/picture does not require an access token in V2.0 and will work even when <user id> is the application area identifier

The identifier provided must be the actual user ID or application associated with the application. A response from /<user id>/invitable_friends or /<user_id>/taggable_friends will not work in the same way

Both of these APIs will also return you the full URL of an attractive or user-tagged photo as part of the response, however.

+1
source share

It works great with original user IDs. For identifiers with applications, I did not understand how to use them.

While http://graph.facebook.com/v2.0/APP_SCOPED_ID/picture should work with the new application area identifiers, I can get this answer:

{ "error": { "message": "Unsupported get request.", "type": "GraphMethodException", "code": 100 } }

Please note that this answer is different from the response to completely invalid identifiers. If you use an invalid user id, you will receive:

{ "error": { "message": "(#100) No node specified", "type": "OAuthException", "code": 100 } }

EDIT: since May 10, 2014 this is a known bug.

The Graph API is currently running http://graph.facebook.com/v2.0/APP_SCOPED_ID?fields=picture

0
source share

More articles:


All Articles