Closed ecramer closed 5 years ago
Hi @ecramer , Thank you for reporting this issue. We will look into this issue ASAP and inform you about the solution.
Thanks. In case this wasn't clear, it does get thrown as a SecureStorageException
in the end however the type is NullPointerException. The above stacktrace is from the root cause.
Hi @ecramer , I have made some changes that hopefully should fix the issue. As I could not reproduce the bug I had to improvise a little bit. See https://github.com/adorsys/secure-storage-android/pull/54 for the list of changes. Please use version 1.2.1 I will close this issue right now, but if you find something useful or need help feel free to reopen this issue or open another one.
Using version 1.1.1. Have seen this on Android 8 devices (so far)
The null input isn't being provided by us into the setValue function as we already have a null check before calling setValue.