You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am enjoying working with shared_preferences_settings. Thanks for making it available.
I have run into a possible issue when using the example code in my app for the first time after uninstalling the app (which flushes its storage) and then reinstalling it. I encounter a failed assertion in the Settings().onStringChanged example, apparently because "value" is null when the screen is being drawn. If I hack a non-null value in for "value" like this:
Hi Dan,
Thanks for your email. Can you use a workaround, for example, with a null
check? Maybe we need this null check inside the library to avoid such calls.
Barnabas.
On 30 January 2021 17:42:40 GMT, "Barnabás BARTHA" ***@***.***> wrote:
Hi Dan,
Thanks for your email. Can you use a workaround, for example, with a
null
check? Maybe we need this null check inside the library to avoid such
calls.
Barnabas.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#24 (comment)
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Hello,
I am enjoying working with shared_preferences_settings. Thanks for making it available.
I have run into a possible issue when using the example code in my app for the first time after uninstalling the app (which flushes its storage) and then reinstalling it. I encounter a failed assertion in the Settings().onStringChanged example, apparently because "value" is null when the screen is being drawn. If I hack a non-null value in for "value" like this:
and hot reload then the problem goes away. If I revert the hack and hot reload again, the problem reappears.
Note that I have commented out the provider and auth_provider imports as they appear to be unused.
Can you suggest what I might be doing wrong or let me know how to resolve this?
Thanks.
-Dan
The text was updated successfully, but these errors were encountered: