Skip to content

Right after setup, facy runs but after a short while "[Info] Please restart facy to access new access token!" appears. #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
danielrippa opened this issue Apr 10, 2016 · 5 comments

Comments

@danielrippa
Copy link

Windows 10Pro x64
Ruby 2.2.3p173 (2015-08-18 revision 51636) [x64-mingw32]
Gem 2.2.3
Facy 1.2.18

running facy, providing it with app id, app secret, and user access token ends successfully.
Promts with "f >>".
After a short while it says:
[Info] Please restart facy to obtain new access token!
facy going to stop...

.facy_config.yml gets created on C:/tmp/
.facy_access_token.yml DOES NOT get created anywhere (could this be the problem?)

deleting .facy_config.yml and restarting facy does not solve the problem.

deleting .facy_config.yml, gem uninstall facy, and then gem install facy, running facy, does not solve the problem.

access token debugger shows only user_friends, public_profile scopes were granted, says origin unknown, valid true, issued unknown

using long-lived access token from access token debugger does not solve the problem

@timhtheos
Copy link

+1

@muralikodali
Copy link

same problem

@baylesj
Copy link

baylesj commented Aug 23, 2016

+1 same problem.

This appears to be due to the fact that Facy is interacting with the Facebook API in a deprecated manner. From a few minutes of digging, it looks like Facebook now requires a callback URL--not specified in these instructions--for the application, as well as Facy is utilizing permissions that have been removed from the API service, such as manage_notifications.

Please see the list of valid permissions here and correct Facy's request URL:

https://developers.facebook.com/docs/facebook-login/permissions

I will investigate and see if I have time to fix it, as it looks like this project is currently dead.

@vxbinaca
Copy link

vxbinaca commented Sep 4, 2016

Same here too, just died after putting in the user token

@ryanknutson
Copy link

Same here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants