Closed Lovrenc closed 4 years ago
I noticed the lib failed to create a key upon the first setValue because my thread was interrupted so this was my mistake.
I am interested, however, why the lib never tried to recreate the key (on subsequent runs).
I notices the lib failed to create a key upon the first setValue because my thread was interrupted so this was my mistake.
I am interested, however, why the lib never tried to recreate the key (on subsequent runs).
Hi @Lovrenc , The info you gave may be helpful for us finding this "bug" in the future. Could you please give some more info about the device model, OS version etc. so that we could try to reproduce the bug to make the research easier. Thanks for using SecureStorage and contributing.
OpnePlus 6T Android v. 10 OxygenOS 10.3.0
In my case, I had a race condition.
The first interaction with SecurePreferences was called on a separate thread which was wrongly tied to the UI lifecycle and was sometimes disposed of before the key generation code hascompleted.
Version 1.2.4