I?ve sussed it ? and have replicated both the problem and the solution on three different computers.
With QR 2.0ß32 and with 2.0ß33, at least, do the following
without an identity key installed:
1. Create a new archive.
2. Create a capture action which will save files to the new archive.
3. Attempt to run the capture action.
QR will then tell you (and very reasonably, too!) that you need a valid identity key.
4. Get a valid identity key. (In testing, I used both ß32 and ß33 keys.)
5. Enter the identity key in the QR preferences.
6. Again try to run the capture action.
Surprisingly, one then sees the same warning one saw after step #3:
Capture requires an identity key
The identity key is missing or invalid. Enter a valid identity
key in the QRecall preferences.
At this point, the only way I?ve found to proceed is to:
7. Quit QRecall.
8. Quit its ?monitor? and ?schedule? processes via Activity Monitor.
9. Move
all QRecall files to the trash & empty the trash (include System files in the Spotlight search to find everything).
10. Reboot.
11. Install QRecall.
12. Add the identity key in preferences.
13. Then resume with step #1 above.
Sorry to report the bug ? but
very happy to prove that it wasn?t my imagination!
This is all with OS X 10.11.3, running on a 2009 MacBook Pro, a 2009 Mac Mini, and a 2011 Mac Mini, with source files and destination archives set up in various combinations of pushing over a network, pulling over a network, and backing up locally. 100% consistent.
Now that I?ve worked this out, I?ll resume exploring this very fine program....
------
I?ve changed the subject of the first post here from
Identity key ?invalid? for backing up networked volume to a local archive? to
Causing QR to prompt for an identity key renders it incapable of using a newly entered key