QRecall 2.2 has been tested under Big Sur and appears to be generally functional. We're performed hundreds of captures here at QRecall central.
There may be some odd issues with the layers.index file (see the earlier thread), which we're looking into. But for now it appears that repairing the archive will resolve the issue (and this issue does not involve any data loss).
As mentioned in the
2.2.8 release notes, there are a few minor cosmetic issues, most of which are being dealt with in QRecall 3.0 (which has not been released yet).