Clarification about API keys

I didn't realize it was so confusing or I would have tried to provide clearer instructions. There are two separate command line options for telling Zowie new values of the user id and api key: -i, and -a. The first (-i) is for giving the Zotero user ID, and the second (-a) is for giving the API key. To force Zowie to remember new values, just run it again with the flags followed by the new values, more or less like this:

    zowie  -i myuserid  -a myapikey  ~/Zotero

An actual value for "myuserid" will be a 7 or maybe 8 digit number like "7340123". A value for "myapikey" will be look like "1ydtqmMZnWkxuLYFoanDJpJe", so you would type something like this (don't use these values -- these are just fake examples):

    zowie  -i 7340123  -a 1ydtqmMZnWkxuLYFoanDJpJe  ~/Zotero

They are stored in the macOS keychain so that you don't have to keep supplying them on every run. On subsequent invocations of Zowie, you can just type

    zowie ~/Zotero

and it should work.

If you continue to have trouble with the permissions, you may be able to get more information about why it's happening by giving the debug flag to Zowie:

    zowie  -@ -  ~/Zotero

Note the dash alone by itself after -@. It means "send the output to the terminal". Instead of the dash, you can send the output to a file, for example like this:

    zowie  -@ ~/zowie-debug.txt  ~/Zotero

The debug output is very technical, but it may be possible for you to infer the cause of a problem by reading what Zowie logged near the end of the debug output, shortly before it quit.