viewDidLoad called twice, using navigation controller
up vote
0
down vote
favorite
My ViewDidLoad
method on a ViewController
is called twice, but only in a particular scenario. There are two view controllers which I need to present, one if user isn't logged in and the second if the user is logged in. I am using storyboard and have set a navigation controller as initial view controller in it.
In my AppDelegate
didFinishLaunchingWithOptions
method I have populated ViewControllers
array with the desired controller as below
let storyboard = UIStoryboard(name: "Main", bundle: nil)
let navigationController = storyboard.instantiateViewController(withIdentifier: "navController") as! UINavigationController
if UserDefaults.standard.object(forKey: USERID) != nil {
viewController = storyboard.instantiateViewController(withIdentifier: "HomeVC_ID") as! HomeVC
}
else {
viewController = storyboard.instantiateViewController(withIdentifier: "LoginVC_ID") as! LoginVC
}
navigationController.viewControllers = [viewController] as! [UIViewController]
self.window?.rootViewController = navigationController
self.window?.makeKeyAndVisible()
ViewDidLoad
method in HomeVC
is called twice, whereas it's called just once for LoginVC
.
I already tried searching through articles viewDidLoad is called twice and viewDidLoad getting called twice on rootViewController at launch but couldn't corner the issue.
ios swift uinavigationcontroller rootviewcontroller
|
show 5 more comments
up vote
0
down vote
favorite
My ViewDidLoad
method on a ViewController
is called twice, but only in a particular scenario. There are two view controllers which I need to present, one if user isn't logged in and the second if the user is logged in. I am using storyboard and have set a navigation controller as initial view controller in it.
In my AppDelegate
didFinishLaunchingWithOptions
method I have populated ViewControllers
array with the desired controller as below
let storyboard = UIStoryboard(name: "Main", bundle: nil)
let navigationController = storyboard.instantiateViewController(withIdentifier: "navController") as! UINavigationController
if UserDefaults.standard.object(forKey: USERID) != nil {
viewController = storyboard.instantiateViewController(withIdentifier: "HomeVC_ID") as! HomeVC
}
else {
viewController = storyboard.instantiateViewController(withIdentifier: "LoginVC_ID") as! LoginVC
}
navigationController.viewControllers = [viewController] as! [UIViewController]
self.window?.rootViewController = navigationController
self.window?.makeKeyAndVisible()
ViewDidLoad
method in HomeVC
is called twice, whereas it's called just once for LoginVC
.
I already tried searching through articles viewDidLoad is called twice and viewDidLoad getting called twice on rootViewController at launch but couldn't corner the issue.
ios swift uinavigationcontroller rootviewcontroller
1
I think this is due to segue in Storyboard.
– Rizwan
Nov 19 at 8:11
I have ticked "Is Initial View Controller" for navigation controller. No other segue used. If I remove it, it shows a black screen on loading.
– Sam
Nov 19 at 8:16
if you setting root view controller programmatically then remove main interface from Deployment Info.
– Jatin Kathrotiya
Nov 19 at 8:20
Maybe theUITabViewController
is better for your UI design. You can hide tab button and control it by codes.
– AechoLiu
Nov 19 at 9:28
@JatinKathrotiya Removing "Main Storyboard file base name" presents a black screen after splash.
– Sam
Nov 19 at 10:00
|
show 5 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
My ViewDidLoad
method on a ViewController
is called twice, but only in a particular scenario. There are two view controllers which I need to present, one if user isn't logged in and the second if the user is logged in. I am using storyboard and have set a navigation controller as initial view controller in it.
In my AppDelegate
didFinishLaunchingWithOptions
method I have populated ViewControllers
array with the desired controller as below
let storyboard = UIStoryboard(name: "Main", bundle: nil)
let navigationController = storyboard.instantiateViewController(withIdentifier: "navController") as! UINavigationController
if UserDefaults.standard.object(forKey: USERID) != nil {
viewController = storyboard.instantiateViewController(withIdentifier: "HomeVC_ID") as! HomeVC
}
else {
viewController = storyboard.instantiateViewController(withIdentifier: "LoginVC_ID") as! LoginVC
}
navigationController.viewControllers = [viewController] as! [UIViewController]
self.window?.rootViewController = navigationController
self.window?.makeKeyAndVisible()
ViewDidLoad
method in HomeVC
is called twice, whereas it's called just once for LoginVC
.
I already tried searching through articles viewDidLoad is called twice and viewDidLoad getting called twice on rootViewController at launch but couldn't corner the issue.
ios swift uinavigationcontroller rootviewcontroller
My ViewDidLoad
method on a ViewController
is called twice, but only in a particular scenario. There are two view controllers which I need to present, one if user isn't logged in and the second if the user is logged in. I am using storyboard and have set a navigation controller as initial view controller in it.
In my AppDelegate
didFinishLaunchingWithOptions
method I have populated ViewControllers
array with the desired controller as below
let storyboard = UIStoryboard(name: "Main", bundle: nil)
let navigationController = storyboard.instantiateViewController(withIdentifier: "navController") as! UINavigationController
if UserDefaults.standard.object(forKey: USERID) != nil {
viewController = storyboard.instantiateViewController(withIdentifier: "HomeVC_ID") as! HomeVC
}
else {
viewController = storyboard.instantiateViewController(withIdentifier: "LoginVC_ID") as! LoginVC
}
navigationController.viewControllers = [viewController] as! [UIViewController]
self.window?.rootViewController = navigationController
self.window?.makeKeyAndVisible()
ViewDidLoad
method in HomeVC
is called twice, whereas it's called just once for LoginVC
.
I already tried searching through articles viewDidLoad is called twice and viewDidLoad getting called twice on rootViewController at launch but couldn't corner the issue.
ios swift uinavigationcontroller rootviewcontroller
ios swift uinavigationcontroller rootviewcontroller
edited Nov 19 at 9:38
Denis
38814
38814
asked Nov 19 at 8:02
Sam
131317
131317
1
I think this is due to segue in Storyboard.
– Rizwan
Nov 19 at 8:11
I have ticked "Is Initial View Controller" for navigation controller. No other segue used. If I remove it, it shows a black screen on loading.
– Sam
Nov 19 at 8:16
if you setting root view controller programmatically then remove main interface from Deployment Info.
– Jatin Kathrotiya
Nov 19 at 8:20
Maybe theUITabViewController
is better for your UI design. You can hide tab button and control it by codes.
– AechoLiu
Nov 19 at 9:28
@JatinKathrotiya Removing "Main Storyboard file base name" presents a black screen after splash.
– Sam
Nov 19 at 10:00
|
show 5 more comments
1
I think this is due to segue in Storyboard.
– Rizwan
Nov 19 at 8:11
I have ticked "Is Initial View Controller" for navigation controller. No other segue used. If I remove it, it shows a black screen on loading.
– Sam
Nov 19 at 8:16
if you setting root view controller programmatically then remove main interface from Deployment Info.
– Jatin Kathrotiya
Nov 19 at 8:20
Maybe theUITabViewController
is better for your UI design. You can hide tab button and control it by codes.
– AechoLiu
Nov 19 at 9:28
@JatinKathrotiya Removing "Main Storyboard file base name" presents a black screen after splash.
– Sam
Nov 19 at 10:00
1
1
I think this is due to segue in Storyboard.
– Rizwan
Nov 19 at 8:11
I think this is due to segue in Storyboard.
– Rizwan
Nov 19 at 8:11
I have ticked "Is Initial View Controller" for navigation controller. No other segue used. If I remove it, it shows a black screen on loading.
– Sam
Nov 19 at 8:16
I have ticked "Is Initial View Controller" for navigation controller. No other segue used. If I remove it, it shows a black screen on loading.
– Sam
Nov 19 at 8:16
if you setting root view controller programmatically then remove main interface from Deployment Info.
– Jatin Kathrotiya
Nov 19 at 8:20
if you setting root view controller programmatically then remove main interface from Deployment Info.
– Jatin Kathrotiya
Nov 19 at 8:20
Maybe the
UITabViewController
is better for your UI design. You can hide tab button and control it by codes.– AechoLiu
Nov 19 at 9:28
Maybe the
UITabViewController
is better for your UI design. You can hide tab button and control it by codes.– AechoLiu
Nov 19 at 9:28
@JatinKathrotiya Removing "Main Storyboard file base name" presents a black screen after splash.
– Sam
Nov 19 at 10:00
@JatinKathrotiya Removing "Main Storyboard file base name" presents a black screen after splash.
– Sam
Nov 19 at 10:00
|
show 5 more comments
2 Answers
2
active
oldest
votes
up vote
2
down vote
accepted
When you create your navigation view controller from the storyboard, this already contains it's rootViewController
(which must not to be confused with the rootViewController
of the UIWindow
). I guess this is your HomeVC
(in the storyboard). So, the storyboard magic already creates HomeVC
, and you do not have to create it manually in didFinishLaunchingWithOptions
.
If you have specify the storyboard as your main interface in the project's/target's properties, you do not need any creational code in didFinishLaunchingWithOptions
and just let the framework perform the magic.
If you want to do this programatically, then - in the storyboard - you should remove the navigation controller, and create it manually (not via instantiateViewController
) in didFinishLaunchingWithOptions
. You would also add the appropriate root view controller here (instantiated from the storyboard), maybe like this:
let storyboard = UIStoryboard(name: "Main", bundle: nil)
if UserDefaults.standard.object(forKey: USERID) != nil {
viewController = storyboard.instantiateViewController(withIdentifier: "HomeVC_ID") as! HomeVC
} else {
viewController = storyboard.instantiateViewController(withIdentifier: "LoginVC_ID") as! LoginVC
}
let navigationController = UINavigationController(rootViewController:viewController)
self.window?.rootViewController = navigationController
self.window?.makeKeyAndVisible()
thanks. I removed navigation controller from storyboard and created the same manually, but the issue still repeats. On auto-login when control directly goes to the HomeVC, viewDidLoad is called just once, as desired. But in case of first time login, when it navigates from LoginVC, then its called twice.
– Sam
Nov 19 at 11:07
add a comment |
up vote
0
down vote
I would recommend don't do any manual segue OR load view controller in app delegate. Use following piece of code in viewDidLoad of LoginView (hoping this is root view of your app always).
Use segue for login to homeview.
if UserDefaults.standard.object(forKey: USERID) != nil {
self.performSegue(withIdentifier: "HomeViewIdentifier", sender: self)
}
Considering HomeViewIdentifier
is a segueId
for LoginView
to HomeView
.
Why I am suggesting this because you need to segue back to loginView
when user logs out. In case you make homeView
as rootview
then where will you go in case of logout.
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
When you create your navigation view controller from the storyboard, this already contains it's rootViewController
(which must not to be confused with the rootViewController
of the UIWindow
). I guess this is your HomeVC
(in the storyboard). So, the storyboard magic already creates HomeVC
, and you do not have to create it manually in didFinishLaunchingWithOptions
.
If you have specify the storyboard as your main interface in the project's/target's properties, you do not need any creational code in didFinishLaunchingWithOptions
and just let the framework perform the magic.
If you want to do this programatically, then - in the storyboard - you should remove the navigation controller, and create it manually (not via instantiateViewController
) in didFinishLaunchingWithOptions
. You would also add the appropriate root view controller here (instantiated from the storyboard), maybe like this:
let storyboard = UIStoryboard(name: "Main", bundle: nil)
if UserDefaults.standard.object(forKey: USERID) != nil {
viewController = storyboard.instantiateViewController(withIdentifier: "HomeVC_ID") as! HomeVC
} else {
viewController = storyboard.instantiateViewController(withIdentifier: "LoginVC_ID") as! LoginVC
}
let navigationController = UINavigationController(rootViewController:viewController)
self.window?.rootViewController = navigationController
self.window?.makeKeyAndVisible()
thanks. I removed navigation controller from storyboard and created the same manually, but the issue still repeats. On auto-login when control directly goes to the HomeVC, viewDidLoad is called just once, as desired. But in case of first time login, when it navigates from LoginVC, then its called twice.
– Sam
Nov 19 at 11:07
add a comment |
up vote
2
down vote
accepted
When you create your navigation view controller from the storyboard, this already contains it's rootViewController
(which must not to be confused with the rootViewController
of the UIWindow
). I guess this is your HomeVC
(in the storyboard). So, the storyboard magic already creates HomeVC
, and you do not have to create it manually in didFinishLaunchingWithOptions
.
If you have specify the storyboard as your main interface in the project's/target's properties, you do not need any creational code in didFinishLaunchingWithOptions
and just let the framework perform the magic.
If you want to do this programatically, then - in the storyboard - you should remove the navigation controller, and create it manually (not via instantiateViewController
) in didFinishLaunchingWithOptions
. You would also add the appropriate root view controller here (instantiated from the storyboard), maybe like this:
let storyboard = UIStoryboard(name: "Main", bundle: nil)
if UserDefaults.standard.object(forKey: USERID) != nil {
viewController = storyboard.instantiateViewController(withIdentifier: "HomeVC_ID") as! HomeVC
} else {
viewController = storyboard.instantiateViewController(withIdentifier: "LoginVC_ID") as! LoginVC
}
let navigationController = UINavigationController(rootViewController:viewController)
self.window?.rootViewController = navigationController
self.window?.makeKeyAndVisible()
thanks. I removed navigation controller from storyboard and created the same manually, but the issue still repeats. On auto-login when control directly goes to the HomeVC, viewDidLoad is called just once, as desired. But in case of first time login, when it navigates from LoginVC, then its called twice.
– Sam
Nov 19 at 11:07
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
When you create your navigation view controller from the storyboard, this already contains it's rootViewController
(which must not to be confused with the rootViewController
of the UIWindow
). I guess this is your HomeVC
(in the storyboard). So, the storyboard magic already creates HomeVC
, and you do not have to create it manually in didFinishLaunchingWithOptions
.
If you have specify the storyboard as your main interface in the project's/target's properties, you do not need any creational code in didFinishLaunchingWithOptions
and just let the framework perform the magic.
If you want to do this programatically, then - in the storyboard - you should remove the navigation controller, and create it manually (not via instantiateViewController
) in didFinishLaunchingWithOptions
. You would also add the appropriate root view controller here (instantiated from the storyboard), maybe like this:
let storyboard = UIStoryboard(name: "Main", bundle: nil)
if UserDefaults.standard.object(forKey: USERID) != nil {
viewController = storyboard.instantiateViewController(withIdentifier: "HomeVC_ID") as! HomeVC
} else {
viewController = storyboard.instantiateViewController(withIdentifier: "LoginVC_ID") as! LoginVC
}
let navigationController = UINavigationController(rootViewController:viewController)
self.window?.rootViewController = navigationController
self.window?.makeKeyAndVisible()
When you create your navigation view controller from the storyboard, this already contains it's rootViewController
(which must not to be confused with the rootViewController
of the UIWindow
). I guess this is your HomeVC
(in the storyboard). So, the storyboard magic already creates HomeVC
, and you do not have to create it manually in didFinishLaunchingWithOptions
.
If you have specify the storyboard as your main interface in the project's/target's properties, you do not need any creational code in didFinishLaunchingWithOptions
and just let the framework perform the magic.
If you want to do this programatically, then - in the storyboard - you should remove the navigation controller, and create it manually (not via instantiateViewController
) in didFinishLaunchingWithOptions
. You would also add the appropriate root view controller here (instantiated from the storyboard), maybe like this:
let storyboard = UIStoryboard(name: "Main", bundle: nil)
if UserDefaults.standard.object(forKey: USERID) != nil {
viewController = storyboard.instantiateViewController(withIdentifier: "HomeVC_ID") as! HomeVC
} else {
viewController = storyboard.instantiateViewController(withIdentifier: "LoginVC_ID") as! LoginVC
}
let navigationController = UINavigationController(rootViewController:viewController)
self.window?.rootViewController = navigationController
self.window?.makeKeyAndVisible()
edited Nov 19 at 8:28
answered Nov 19 at 8:21
Andreas Oetjen
3,89111125
3,89111125
thanks. I removed navigation controller from storyboard and created the same manually, but the issue still repeats. On auto-login when control directly goes to the HomeVC, viewDidLoad is called just once, as desired. But in case of first time login, when it navigates from LoginVC, then its called twice.
– Sam
Nov 19 at 11:07
add a comment |
thanks. I removed navigation controller from storyboard and created the same manually, but the issue still repeats. On auto-login when control directly goes to the HomeVC, viewDidLoad is called just once, as desired. But in case of first time login, when it navigates from LoginVC, then its called twice.
– Sam
Nov 19 at 11:07
thanks. I removed navigation controller from storyboard and created the same manually, but the issue still repeats. On auto-login when control directly goes to the HomeVC, viewDidLoad is called just once, as desired. But in case of first time login, when it navigates from LoginVC, then its called twice.
– Sam
Nov 19 at 11:07
thanks. I removed navigation controller from storyboard and created the same manually, but the issue still repeats. On auto-login when control directly goes to the HomeVC, viewDidLoad is called just once, as desired. But in case of first time login, when it navigates from LoginVC, then its called twice.
– Sam
Nov 19 at 11:07
add a comment |
up vote
0
down vote
I would recommend don't do any manual segue OR load view controller in app delegate. Use following piece of code in viewDidLoad of LoginView (hoping this is root view of your app always).
Use segue for login to homeview.
if UserDefaults.standard.object(forKey: USERID) != nil {
self.performSegue(withIdentifier: "HomeViewIdentifier", sender: self)
}
Considering HomeViewIdentifier
is a segueId
for LoginView
to HomeView
.
Why I am suggesting this because you need to segue back to loginView
when user logs out. In case you make homeView
as rootview
then where will you go in case of logout.
add a comment |
up vote
0
down vote
I would recommend don't do any manual segue OR load view controller in app delegate. Use following piece of code in viewDidLoad of LoginView (hoping this is root view of your app always).
Use segue for login to homeview.
if UserDefaults.standard.object(forKey: USERID) != nil {
self.performSegue(withIdentifier: "HomeViewIdentifier", sender: self)
}
Considering HomeViewIdentifier
is a segueId
for LoginView
to HomeView
.
Why I am suggesting this because you need to segue back to loginView
when user logs out. In case you make homeView
as rootview
then where will you go in case of logout.
add a comment |
up vote
0
down vote
up vote
0
down vote
I would recommend don't do any manual segue OR load view controller in app delegate. Use following piece of code in viewDidLoad of LoginView (hoping this is root view of your app always).
Use segue for login to homeview.
if UserDefaults.standard.object(forKey: USERID) != nil {
self.performSegue(withIdentifier: "HomeViewIdentifier", sender: self)
}
Considering HomeViewIdentifier
is a segueId
for LoginView
to HomeView
.
Why I am suggesting this because you need to segue back to loginView
when user logs out. In case you make homeView
as rootview
then where will you go in case of logout.
I would recommend don't do any manual segue OR load view controller in app delegate. Use following piece of code in viewDidLoad of LoginView (hoping this is root view of your app always).
Use segue for login to homeview.
if UserDefaults.standard.object(forKey: USERID) != nil {
self.performSegue(withIdentifier: "HomeViewIdentifier", sender: self)
}
Considering HomeViewIdentifier
is a segueId
for LoginView
to HomeView
.
Why I am suggesting this because you need to segue back to loginView
when user logs out. In case you make homeView
as rootview
then where will you go in case of logout.
edited Nov 19 at 8:31
answered Nov 19 at 8:26
Rizwan
1,240418
1,240418
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%2f53370504%2fviewdidload-called-twice-using-navigation-controller%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
1
I think this is due to segue in Storyboard.
– Rizwan
Nov 19 at 8:11
I have ticked "Is Initial View Controller" for navigation controller. No other segue used. If I remove it, it shows a black screen on loading.
– Sam
Nov 19 at 8:16
if you setting root view controller programmatically then remove main interface from Deployment Info.
– Jatin Kathrotiya
Nov 19 at 8:20
Maybe the
UITabViewController
is better for your UI design. You can hide tab button and control it by codes.– AechoLiu
Nov 19 at 9:28
@JatinKathrotiya Removing "Main Storyboard file base name" presents a black screen after splash.
– Sam
Nov 19 at 10:00