Comment 11 for bug 1453549

I'm back with more information.

The shotwell code is correct, as far as I can tell. The reason why it's failing is because the access token it gets only carries the permissions to see the public profile, and not the permissions to publich photos or videos. Why this happens, I'm not sure.

My guess is that the Shotwell application in not properly registered in the Facebook servers to comply with the v2.0 API. As far as I know, only Yorba has access to that key, so there isn't much we can do about it.

I've tried playing with the authorization URL (note: you should first remove Shotwell from your profile at https://www.facebook.com/settings?tab=applications):

https://www.facebook.com//dialog/oauth?client_id=162702932093&redirect_uri=https://www.facebook.com/connect/login_success.html&response_type=token&scope=publish_actions,user_photos,user_videos
 and it seems that it always ignores the permissions ("scope" parameter) we request.

Incidentally, I discovered a bug in our Online Accounts integration with Shotwell, which causes the application to retry the authentication forever when the access to the application is revoked from the facebook site. The attached branch fixes this.