-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
App problem finding bibcodes #17
Comments
It sounds like the query found a non-single match (and the query request did work, otherwise, an API response error will be returned): Could you try |
That command loaded the requested article successfully. I got the original error by clicking on the "add to bibdesk" app. I must have had the API key highlighted when I should have had a bibcode highlighted. So this has nothing to do with the API key (thus I have edited the issue title). However, I am still getting the same error if I do have a valid bibcode highlighted when I click on the app: 2021-06-17 13:31:13 ads2bibdesk.ads2bibdesk.main [INFO] : Starting ADS to BibDesk |
This might be the known issue related to the macOS privacy feature (see README.rst and #8), which could prevent one app to access text from another app. |
Yep, Catalina. I was trying to use the app to access text highlighted in Google Chrome, though, which is listed as OK in the referenced issue. Well, I guess I can live with the CLI, so let me not take up any more of your time. |
I am getting the following error message in the log, and nothing happens.
2021-06-17 11:48:14 ads2bibdesk.ads2bibdesk.main [INFO] : Starting ADS to BibDesk
2021-06-17 11:48:25 ads2bibdesk.ads2bibdesk.process_token [INFO] : Found Zero or Multiple ADS antries for [valid API key]
2021-06-17 11:48:25 ads2bibdesk.ads2bibdesk.process_token [INFO] : No update in BibDesk
I just created the .ads directory (so no pre-existing files present) and added my brand new API key from ADS to ads2bibdesk.cfg, but still got this error.
The text was updated successfully, but these errors were encountered: