Skip to content
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

Profile "defbbbb" not found #89

Open
davidcsterratt opened this issue Dec 14, 2015 · 1 comment
Open

Profile "defbbbb" not found #89

davidcsterratt opened this issue Dec 14, 2015 · 1 comment

Comments

@davidcsterratt
Copy link

I've run into the following error after upgrading to the latest git master branch version of Asynk when trying to sync BBDB to Google Contacts. It's a while (some months) since I last did a sync, so I wonder if I missed out on doing some sort of upgrade to my config?

 $  python2.7 /home/dcs/src/emacs/ASynK/asynk.py --dry-run   --op=sync --gcpwd=XXXX
Applying base config from file /home/dcs/src/emacs/ASynK/config/config_v8.json...
Applying base config from file /home/dcs/src/emacs/ASynK/config/config_v8.json...done
Applying user customizations from file /home/dcs/.asynk/config.py...
Applying user customizations from file /home/dcs/.asynk/config.py...done
[12:25:25.808     INFO] Debug logging to file: /home/dcs/.asynk/logs/asynk_logs.2015-12-14.12-25-25.808445
[12:25:25.814 CRITICAL] Error in User input: Profile "defbbbb" not found
@skarra
Copy link
Owner

skarra commented Mar 6, 2017

My guess is you tried to run ASynK on a new machine. If that is the case the fix would be for you to find the ~/.asynk folder from your other machine or account and copy it to your local machine. This will ensure your next sync can pick up where you left off last time.

A second possibility is in your previous attempts, you ran ASynK by specifying a --user-dir=xxx flag on the command line. If this is case you need to find where that directory is and use the appropriate flag again. Otherwise you will be missing the state and your sync will be pretty badly messed up...

A third possibility is a ASynK bug. If you have ruled out both of the above possibilities, I may have to look at your ~/.asynk/state.json. Let's get to this as the last resort.

BTW - Google deprecated the use of username/password with this API a while back. Please refer to this documentation page: https://github.com/skarra/ASynK/blob/master/README-google-oauth.md

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

2 participants