-
Notifications
You must be signed in to change notification settings - Fork 233
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
Existing password item in OSX keychain not found #88
Comments
@laghee Please could you run the following command from an OSX terminal window? This is the underlying command used to retrieve Keychain passwords. Thanks. |
@martintoreilly OK, yep, that command successfully retrieves the token. |
Thanks. I'm not sure what's going on yet. I've done some digging around and I think the
|
Oh, interesting. Yes, if I change the value of the where field to |
It looks like the error is not the command, that's correct as has been confirmed by running it from the command line. Turns out it's an exception being thrown on the next line: Here's the exception (I just added a call to
When I log the Adding the following before concatenating the token fixes the issue:
Submitting a PR now :) |
@josegonzalez Looks like my "closes" line in the PR comment didn't automatically close this issue, but it can be closed now that this is merged. |
I followed all the steps in the doc on creating a osx keychain password item, but when I run the following command:
github-backup $ORG --keychain-name ghbackup --keychain-account laghee -o ./data --issues --issue-events --milestones --labels -R $REPO
I keep getting this error:
No password item matching the provided name and account could be found in the osx keychain.
This is my password item:
I'm on MacOS HighSierra (10.13.5).
Is there some other field that needs to be modified that isn't mentioned in the docs?
Since I only need to run one backup at the moment, I directly entered my credentials with the
--username
and--token
flags, and that worked fine. But if I ever had to run several or set a script to back up automatically ... this would be a problem.The text was updated successfully, but these errors were encountered: