How to read value in the createState method of StatefulWidget
up vote
1
down vote
favorite
Hello I want to read the value from the SharedPreferences inside the createState
of the StatefulWidget
.
I tried to add async
after the method but it doesn't work. What is the correct way to do ?
class LoginScreen extends StatefulWidget {
@override
_LoginScreenState createState() {
// check if user is logged. If logged then send user to dashboard else keep it here
return new _LoginScreenState();
}
}
android ios flutter sharedpreferences
add a comment |
up vote
1
down vote
favorite
Hello I want to read the value from the SharedPreferences inside the createState
of the StatefulWidget
.
I tried to add async
after the method but it doesn't work. What is the correct way to do ?
class LoginScreen extends StatefulWidget {
@override
_LoginScreenState createState() {
// check if user is logged. If logged then send user to dashboard else keep it here
return new _LoginScreenState();
}
}
android ios flutter sharedpreferences
That's not a good idea. Do it ininitState()
of_LoginScreenState()
instead.
– Günter Zöchbauer
Nov 22 at 16:53
How to do there ?
– N Sharma
Nov 22 at 16:56
Nothing special, just do it and usesetState(() { ...})
to update the value when it's available. This is a FAQ and there should be several answers for that on StackOverflow already.
– Günter Zöchbauer
Nov 22 at 16:58
1
I'd usedidChangeDependencies
instead in case the user disconnect. User details most likely comes from an InheritedWidget anyway
– Rémi Rousselet
Nov 22 at 17:03
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Hello I want to read the value from the SharedPreferences inside the createState
of the StatefulWidget
.
I tried to add async
after the method but it doesn't work. What is the correct way to do ?
class LoginScreen extends StatefulWidget {
@override
_LoginScreenState createState() {
// check if user is logged. If logged then send user to dashboard else keep it here
return new _LoginScreenState();
}
}
android ios flutter sharedpreferences
Hello I want to read the value from the SharedPreferences inside the createState
of the StatefulWidget
.
I tried to add async
after the method but it doesn't work. What is the correct way to do ?
class LoginScreen extends StatefulWidget {
@override
_LoginScreenState createState() {
// check if user is logged. If logged then send user to dashboard else keep it here
return new _LoginScreenState();
}
}
android ios flutter sharedpreferences
android ios flutter sharedpreferences
asked Nov 22 at 16:52
N Sharma
6,97243141289
6,97243141289
That's not a good idea. Do it ininitState()
of_LoginScreenState()
instead.
– Günter Zöchbauer
Nov 22 at 16:53
How to do there ?
– N Sharma
Nov 22 at 16:56
Nothing special, just do it and usesetState(() { ...})
to update the value when it's available. This is a FAQ and there should be several answers for that on StackOverflow already.
– Günter Zöchbauer
Nov 22 at 16:58
1
I'd usedidChangeDependencies
instead in case the user disconnect. User details most likely comes from an InheritedWidget anyway
– Rémi Rousselet
Nov 22 at 17:03
add a comment |
That's not a good idea. Do it ininitState()
of_LoginScreenState()
instead.
– Günter Zöchbauer
Nov 22 at 16:53
How to do there ?
– N Sharma
Nov 22 at 16:56
Nothing special, just do it and usesetState(() { ...})
to update the value when it's available. This is a FAQ and there should be several answers for that on StackOverflow already.
– Günter Zöchbauer
Nov 22 at 16:58
1
I'd usedidChangeDependencies
instead in case the user disconnect. User details most likely comes from an InheritedWidget anyway
– Rémi Rousselet
Nov 22 at 17:03
That's not a good idea. Do it in
initState()
of _LoginScreenState()
instead.– Günter Zöchbauer
Nov 22 at 16:53
That's not a good idea. Do it in
initState()
of _LoginScreenState()
instead.– Günter Zöchbauer
Nov 22 at 16:53
How to do there ?
– N Sharma
Nov 22 at 16:56
How to do there ?
– N Sharma
Nov 22 at 16:56
Nothing special, just do it and use
setState(() { ...})
to update the value when it's available. This is a FAQ and there should be several answers for that on StackOverflow already.– Günter Zöchbauer
Nov 22 at 16:58
Nothing special, just do it and use
setState(() { ...})
to update the value when it's available. This is a FAQ and there should be several answers for that on StackOverflow already.– Günter Zöchbauer
Nov 22 at 16:58
1
1
I'd use
didChangeDependencies
instead in case the user disconnect. User details most likely comes from an InheritedWidget anyway– Rémi Rousselet
Nov 22 at 17:03
I'd use
didChangeDependencies
instead in case the user disconnect. User details most likely comes from an InheritedWidget anyway– Rémi Rousselet
Nov 22 at 17:03
add a comment |
2 Answers
2
active
oldest
votes
up vote
3
down vote
You don't.
You should not have anything inside createState
beside the state creation. If you want to do these kind of check, do them inside the State
class instead:
class MyState extends State<MyWidget> {
@override
void didChangeDependencies() {
// check if the user is logged
}
}
add a comment |
up vote
1
down vote
Don't use createState to read the values, you can use initState
or FutureBuilder
maybe.
class LoginScreen extends StatefulWidget {
@override
_LoginScreenState createState() => _LoginScreenState();
}
class _LoginScreenState extends State<LoginScreen> {
String value;
_readPreference() async {
SharedPreferences prefs = await SharedPreferences.getInstance();
//refresh your screen based on the current parameter
setState(() {
value = prefs.getString("your_value_key");
});
}
@override
void initState() {
_readPreference();
super.initState();
}
@override
Widget build(BuildContext context) {
return Container();
}
}
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53435391%2fhow-to-read-value-in-the-createstate-method-of-statefulwidget%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
You don't.
You should not have anything inside createState
beside the state creation. If you want to do these kind of check, do them inside the State
class instead:
class MyState extends State<MyWidget> {
@override
void didChangeDependencies() {
// check if the user is logged
}
}
add a comment |
up vote
3
down vote
You don't.
You should not have anything inside createState
beside the state creation. If you want to do these kind of check, do them inside the State
class instead:
class MyState extends State<MyWidget> {
@override
void didChangeDependencies() {
// check if the user is logged
}
}
add a comment |
up vote
3
down vote
up vote
3
down vote
You don't.
You should not have anything inside createState
beside the state creation. If you want to do these kind of check, do them inside the State
class instead:
class MyState extends State<MyWidget> {
@override
void didChangeDependencies() {
// check if the user is logged
}
}
You don't.
You should not have anything inside createState
beside the state creation. If you want to do these kind of check, do them inside the State
class instead:
class MyState extends State<MyWidget> {
@override
void didChangeDependencies() {
// check if the user is logged
}
}
answered Nov 22 at 17:02
Rémi Rousselet
22.7k24076
22.7k24076
add a comment |
add a comment |
up vote
1
down vote
Don't use createState to read the values, you can use initState
or FutureBuilder
maybe.
class LoginScreen extends StatefulWidget {
@override
_LoginScreenState createState() => _LoginScreenState();
}
class _LoginScreenState extends State<LoginScreen> {
String value;
_readPreference() async {
SharedPreferences prefs = await SharedPreferences.getInstance();
//refresh your screen based on the current parameter
setState(() {
value = prefs.getString("your_value_key");
});
}
@override
void initState() {
_readPreference();
super.initState();
}
@override
Widget build(BuildContext context) {
return Container();
}
}
add a comment |
up vote
1
down vote
Don't use createState to read the values, you can use initState
or FutureBuilder
maybe.
class LoginScreen extends StatefulWidget {
@override
_LoginScreenState createState() => _LoginScreenState();
}
class _LoginScreenState extends State<LoginScreen> {
String value;
_readPreference() async {
SharedPreferences prefs = await SharedPreferences.getInstance();
//refresh your screen based on the current parameter
setState(() {
value = prefs.getString("your_value_key");
});
}
@override
void initState() {
_readPreference();
super.initState();
}
@override
Widget build(BuildContext context) {
return Container();
}
}
add a comment |
up vote
1
down vote
up vote
1
down vote
Don't use createState to read the values, you can use initState
or FutureBuilder
maybe.
class LoginScreen extends StatefulWidget {
@override
_LoginScreenState createState() => _LoginScreenState();
}
class _LoginScreenState extends State<LoginScreen> {
String value;
_readPreference() async {
SharedPreferences prefs = await SharedPreferences.getInstance();
//refresh your screen based on the current parameter
setState(() {
value = prefs.getString("your_value_key");
});
}
@override
void initState() {
_readPreference();
super.initState();
}
@override
Widget build(BuildContext context) {
return Container();
}
}
Don't use createState to read the values, you can use initState
or FutureBuilder
maybe.
class LoginScreen extends StatefulWidget {
@override
_LoginScreenState createState() => _LoginScreenState();
}
class _LoginScreenState extends State<LoginScreen> {
String value;
_readPreference() async {
SharedPreferences prefs = await SharedPreferences.getInstance();
//refresh your screen based on the current parameter
setState(() {
value = prefs.getString("your_value_key");
});
}
@override
void initState() {
_readPreference();
super.initState();
}
@override
Widget build(BuildContext context) {
return Container();
}
}
answered Nov 22 at 17:02
diegoveloper
8,98611225
8,98611225
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53435391%2fhow-to-read-value-in-the-createstate-method-of-statefulwidget%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
That's not a good idea. Do it in
initState()
of_LoginScreenState()
instead.– Günter Zöchbauer
Nov 22 at 16:53
How to do there ?
– N Sharma
Nov 22 at 16:56
Nothing special, just do it and use
setState(() { ...})
to update the value when it's available. This is a FAQ and there should be several answers for that on StackOverflow already.– Günter Zöchbauer
Nov 22 at 16:58
1
I'd use
didChangeDependencies
instead in case the user disconnect. User details most likely comes from an InheritedWidget anyway– Rémi Rousselet
Nov 22 at 17:03