Use requests library instead of manual post/multipart code#39
Use requests library instead of manual post/multipart code#39
Conversation
I couldn't get this working on my machine, thus I will be unable to test it after refactor. Current solution would be to use long lived access tokens obtained through Graph Explorer or otherwise manually. Discuss in #25
|
automatic_authentication is working for me. Happy to work with you to get this working. I think the trick is that a valid URL has to be set for the call back. It doesn't matter what the call back url is. we are using our company home page. Once setup the owner of the app can use his FB login credentials to post to /me/feeds /me/photos without issue. |
|
Hey! This is really good to hear. Can you create a test user & make it work for this user & post it here? My problem when I try to use my account ( just tried) is that throw is happening here: --> 423 raise AutomaticLoginError looks like redirect doesn't happen yet but logic, that needs 'state' tries to kick in. Can you provide details how exactly you managed auto auth to work? + your python, os versions? |
|
Thank you for your pull request. We require contributors to sign our Contributor License Agreement, and yours has expired. Before we can review or merge your code, we need you to email cla@fb.com with your details so we can update your status. |
Summary:
First commit removes automatic auth, since I wasn't able to make it work and can't test it, looks like others have this problem as well ( #25 )
Then just small cleanup for unused imports and main change to use requests
Test Plan:
python setup.py testand make sure authenticate() and shell mode are still working
@bgolub @mduppes @adamgross42
I guess we can use Pull Requests like this for Diff Review