flutter_secure_storage
flutter_secure_storage copied to clipboard
mogol
Do more people see an increase in issues on Samsung Galaxy S21 5G devices?
Starting around October 10 we're seeing an issue on some/all versions of Samsung Galaxy S21 5G devices (e.g. Galaxy S21 Ultra 5G, Galaxy S21 5G, Galaxy S21+ 5G) for our app in the field.
The issue results in users having to setup their app again, every time they open the app (so very annoying user experience, also receiving bad reviews on it). We have a strong suspicion the issue is related to use of this flutter_secure_storage package, or it's underlying used encryption.
But looking at the date the issues started and the devices that are impacted we also have a strong suspicion the issue is related to a recent Samsung Galaxy S21 5G update. Looking at your updates here (S21 5G: https://doc.samsungmobile.com/sm-g991b/xeo/doc.html, and S21 Ultra 5G: https://doc.samsungmobile.com/sm-g998b/dbt/doc.html) we see there were security updates for these devices around the day the issue started.
Do other apps/users of this package also experience a spike of issues in the field?
Hi @PieterAelse, how can I test it? And could you share your [flutter_secure_storage] version?
Yes, same thing here. The impact is big in our user base. We are encountering this exception: #541
We are also experiencing the same issue in our app. Has anyone found an workaround/solution for it yet?
We think we have this issue too, it's killing us as paying subscribers are losing their ID's and so the app thinks they're non-paying 🤦
The workaround we told our users is to uninstall and reinstall the app, that makes the issue go away. However I don't think that's a great solution, would be best to be able to detect that something changed within the flutter_secure_storage library 🤔
@lberaldodev Like also mentioned in the related issue #541, we (and others) don't know a good way to reproduce the issue. Do you happen to have any updates for us? (or for issue #541 )
