When a previously locked module is updated without encryption

During module development and testing the three Bible modules in the Lockman Foundation repository were encrypted (aka "locked") and the unlock keys were shared to members of the CrossWire modules team.

Lockman has graciously allowed these modules to be distributed completely unlocked, and the released versions are now available to install.

For PocketSword users, installing the unlocked version after the locked version had been installed (and even deleted) leaves the new modules unreadable because (presumably) PocketSword had stored the unlock key somewhere in a system configuration file outside the module.

Even a device reboot makes no difference. I suspect the only current means available to the user would be to delete the PocketSword app (losing all its stored modules and other data) and to reinstall it.

This is a very annoying issue. There ought to be a simple means for the app settings to be altered such that it forgets the unlock key for any previously locked module.