@ Colleen
I’ve identified the error and released version 1.0.1 which should correct the issue. It can be downloaded from your purchase history.
Apologies for the trouble.
