Dismiss all Views from NavigationViewController
I have the following setup:
AuthVC || Navigator => TabBarContr => MainVC/SecondVC
=> SettingsVC
In my AuthVC I check if the user is logged in. If yes I just open my Navigator class which is a NavigationViewController and which has my "TabBarContr" as rootview. There I have two TabBarItems. In the Navigationbar of my TabBarContr I have a 'settings' button which opens my SettingsVC. In there I have a logout button. When pressed, I logout and want to kill everything except my authVC-Controller so that I can reopen my login-VC at that point.
What I am doing:
When logout is pressed I link back from my SettingsVC to my TabBarContr. There I call dismissViewController.
I thought this would work because I really get back to my AuthVC. But after logging in again it opens my TabBarContr and there I got some issues loading stuff because some objects are still living from my previous logged-in session.
So what do I need to do to really kill everything except AuthVC?
ios objective-c xcode
asked Nov 13 '18 at 11:19
progNewbieprogNewbie
73241748
add a comment |
I have the following setup:
AuthVC || Navigator => TabBarContr => MainVC/SecondVC
=> SettingsVC
In my AuthVC I check if the user is logged in. If yes I just open my Navigator class which is a NavigationViewController and which has my "TabBarContr" as rootview. There I have two TabBarItems. In the Navigationbar of my TabBarContr I have a 'settings' button which opens my SettingsVC. In there I have a logout button. When pressed, I logout and want to kill everything except my authVC-Controller so that I can reopen my login-VC at that point.
What I am doing:
When logout is pressed I link back from my SettingsVC to my TabBarContr. There I call dismissViewController.
I thought this would work because I really get back to my AuthVC. But after logging in again it opens my TabBarContr and there I got some issues loading stuff because some objects are still living from my previous logged-in session.
So what do I need to do to really kill everything except AuthVC?
ios objective-c xcode
asked Nov 13 '18 at 11:19
progNewbieprogNewbie
73241748
You are presenting allUIViewController's?
– Sohil R. Memon
Nov 13 '18 at 12:01
The flow you have used sounds good to me, but I suspect a memory leak here which is keeping the objects alive.
– hardik parmar
Nov 13 '18 at 12:02
add a comment |
I have the following setup:
AuthVC || Navigator => TabBarContr => MainVC/SecondVC
=> SettingsVC
In my AuthVC I check if the user is logged in. If yes I just open my Navigator class which is a NavigationViewController and which has my "TabBarContr" as rootview. There I have two TabBarItems. In the Navigationbar of my TabBarContr I have a 'settings' button which opens my SettingsVC. In there I have a logout button. When pressed, I logout and want to kill everything except my authVC-Controller so that I can reopen my login-VC at that point.
What I am doing:
When logout is pressed I link back from my SettingsVC to my TabBarContr. There I call dismissViewController.
I thought this would work because I really get back to my AuthVC. But after logging in again it opens my TabBarContr and there I got some issues loading stuff because some objects are still living from my previous logged-in session.
So what do I need to do to really kill everything except AuthVC?
ios objective-c xcode
asked Nov 13 '18 at 11:19
progNewbieprogNewbie
73241748
I have the following setup:
AuthVC || Navigator => TabBarContr => MainVC/SecondVC
=> SettingsVC
In my AuthVC I check if the user is logged in. If yes I just open my Navigator class which is a NavigationViewController and which has my "TabBarContr" as rootview. There I have two TabBarItems. In the Navigationbar of my TabBarContr I have a 'settings' button which opens my SettingsVC. In there I have a logout button. When pressed, I logout and want to kill everything except my authVC-Controller so that I can reopen my login-VC at that point.
What I am doing:
When logout is pressed I link back from my SettingsVC to my TabBarContr. There I call dismissViewController.
I thought this would work because I really get back to my AuthVC. But after logging in again it opens my TabBarContr and there I got some issues loading stuff because some objects are still living from my previous logged-in session.
So what do I need to do to really kill everything except AuthVC?
ios objective-c xcode
ios objective-c xcode
asked Nov 13 '18 at 11:19
progNewbieprogNewbie
73241748
asked Nov 13 '18 at 11:19
progNewbieprogNewbie
73241748
asked Nov 13 '18 at 11:19
progNewbieprogNewbie
73241748
asked Nov 13 '18 at 11:19
progNewbieprogNewbie
73241748
asked Nov 13 '18 at 11:19
progNewbieprogNewbie
73241748
73241748
You are presenting allUIViewController's?
– Sohil R. Memon
Nov 13 '18 at 12:01
The flow you have used sounds good to me, but I suspect a memory leak here which is keeping the objects alive.
– hardik parmar
Nov 13 '18 at 12:02
add a comment |
You are presenting allUIViewController's?
– Sohil R. Memon
Nov 13 '18 at 12:01
The flow you have used sounds good to me, but I suspect a memory leak here which is keeping the objects alive.
– hardik parmar
Nov 13 '18 at 12:02
You are presenting all
UIViewController's?– Sohil R. Memon
Nov 13 '18 at 12:01
You are presenting all
UIViewController's?– Sohil R. Memon
Nov 13 '18 at 12:01
The flow you have used sounds good to me, but I suspect a memory leak here which is keeping the objects alive.
– hardik parmar
Nov 13 '18 at 12:02
The flow you have used sounds good to me, but I suspect a memory leak here which is keeping the objects alive.
– hardik parmar
Nov 13 '18 at 12:02
add a comment |
4 Answers
4
active
oldest
votes
"... But after logging in again it opens my TabBarContr and there I got some issues loading ..."
If I understood you are removing every view, but your problem is your viewcontrollers are not properly restarted. You may have some retained reference so you are reusing the vc objects and then you have some issue presenting them for the second time. Try reviewing what references are not released when you dismiss/pop.
answered Nov 13 '18 at 12:28
Pablo AlegrePablo Alegre
393
Yes correct. That is exactly my problem. Unfortunately I still don't understand why I got retained references and I thought that maybe I can force close the VC so it will not use old objects anymore.
– progNewbie
Nov 13 '18 at 12:36
The typical case is a retained view controller property in the top level, that should be manually set to nil when it is dismissed. If everything is set to nil (try watch object variables debugging) and the problem persists you can also have some cross reference, something like a delegate declared as retained. You can also try to detect wich viewcontroller is not released, overriding dealloc function: -(void)dealloc NSLog( @"class %@ -> deallocn", NSStringFromClass(self.class)); '
– Pablo Alegre
Nov 13 '18 at 12:56
add a comment |
set AuthVC as your window's rootViewController.
let appDelegate = UIApplication.sharedApplication().delegate as! AppDelegate
instantiate AuthVC from storyboard and assign it to window's rootViewController
appDelegate.window?.rootViewController = AuthVC
answered Nov 13 '18 at 11:24
Viren MalhanViren Malhan
7515
you mean rootviewController of my NavigationController? Or do you meaninitial ViewController?
– progNewbie
Nov 13 '18 at 11:28
window's rootViewController. which is present in your app delegate. so your AuthVC will become first screen on window. then you can again continue with your normal navigation flow.
– Viren Malhan
Nov 13 '18 at 11:33
where in my AppDelegate do I set it as rootViewController?
– progNewbie
Nov 13 '18 at 11:36
i have updated my answer. set rootViewController to AVC on logout action.
– Viren Malhan
Nov 13 '18 at 11:57
My AppDelegate is in my Main.class. I set my AuthVC to rootviewcontroller there now. But this does not change anything. I need to do it when the logout button is pressed right? And do I even call dismissviewController anymore?
– progNewbie
Nov 13 '18 at 12:04
|
show 4 more comments
Or you can set root view controller for the window by next code in your settingsVC:
//Did tap logout button
self.view.window?.rootViewController = AuthVC
If it doesn't help you, please send how exactly you show NavigationViewController after AuthVC.
answered Nov 13 '18 at 11:51
GkoluniaGkolunia
828
I'd still need to call dismissViewController right?
– progNewbie
Nov 13 '18 at 12:08
add a comment |
Try this
let maiStoryBoard = UIStoryboard(name: "Main", bundle: nil) //Storyboard in which AuthVC lies
let authVC = mainStoryBoard.instantiateViewControllerWithIdentifier("AuthVC") as! AuthVC
let appDelegate = UIApplication.sharedApplication().delegate as! AppDelegate
appDelegate.window?.rootViewController = authVC
answered Nov 13 '18 at 13:03
SAIFSAIF
617
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',
autoActivateHeartbeat: false,
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%2f53279885%2fdismiss-all-views-from-navigationviewcontroller%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
"... But after logging in again it opens my TabBarContr and there I got some issues loading ..."
If I understood you are removing every view, but your problem is your viewcontrollers are not properly restarted. You may have some retained reference so you are reusing the vc objects and then you have some issue presenting them for the second time. Try reviewing what references are not released when you dismiss/pop.
answered Nov 13 '18 at 12:28
Pablo AlegrePablo Alegre
393
Yes correct. That is exactly my problem. Unfortunately I still don't understand why I got retained references and I thought that maybe I can force close the VC so it will not use old objects anymore.
– progNewbie
Nov 13 '18 at 12:36
The typical case is a retained view controller property in the top level, that should be manually set to nil when it is dismissed. If everything is set to nil (try watch object variables debugging) and the problem persists you can also have some cross reference, something like a delegate declared as retained. You can also try to detect wich viewcontroller is not released, overriding dealloc function: -(void)dealloc NSLog( @"class %@ -> deallocn", NSStringFromClass(self.class)); '
– Pablo Alegre
Nov 13 '18 at 12:56
add a comment |
"... But after logging in again it opens my TabBarContr and there I got some issues loading ..."
If I understood you are removing every view, but your problem is your viewcontrollers are not properly restarted. You may have some retained reference so you are reusing the vc objects and then you have some issue presenting them for the second time. Try reviewing what references are not released when you dismiss/pop.
answered Nov 13 '18 at 12:28
Pablo AlegrePablo Alegre
393
Yes correct. That is exactly my problem. Unfortunately I still don't understand why I got retained references and I thought that maybe I can force close the VC so it will not use old objects anymore.
– progNewbie
Nov 13 '18 at 12:36
The typical case is a retained view controller property in the top level, that should be manually set to nil when it is dismissed. If everything is set to nil (try watch object variables debugging) and the problem persists you can also have some cross reference, something like a delegate declared as retained. You can also try to detect wich viewcontroller is not released, overriding dealloc function: -(void)dealloc NSLog( @"class %@ -> deallocn", NSStringFromClass(self.class)); '
– Pablo Alegre
Nov 13 '18 at 12:56
add a comment |
"... But after logging in again it opens my TabBarContr and there I got some issues loading ..."
If I understood you are removing every view, but your problem is your viewcontrollers are not properly restarted. You may have some retained reference so you are reusing the vc objects and then you have some issue presenting them for the second time. Try reviewing what references are not released when you dismiss/pop.
answered Nov 13 '18 at 12:28
Pablo AlegrePablo Alegre
393
"... But after logging in again it opens my TabBarContr and there I got some issues loading ..."
If I understood you are removing every view, but your problem is your viewcontrollers are not properly restarted. You may have some retained reference so you are reusing the vc objects and then you have some issue presenting them for the second time. Try reviewing what references are not released when you dismiss/pop.
answered Nov 13 '18 at 12:28
Pablo AlegrePablo Alegre
393
answered Nov 13 '18 at 12:28
Pablo AlegrePablo Alegre
393
answered Nov 13 '18 at 12:28
Pablo AlegrePablo Alegre
393
answered Nov 13 '18 at 12:28
Pablo AlegrePablo Alegre
393
393
Yes correct. That is exactly my problem. Unfortunately I still don't understand why I got retained references and I thought that maybe I can force close the VC so it will not use old objects anymore.
– progNewbie
Nov 13 '18 at 12:36
The typical case is a retained view controller property in the top level, that should be manually set to nil when it is dismissed. If everything is set to nil (try watch object variables debugging) and the problem persists you can also have some cross reference, something like a delegate declared as retained. You can also try to detect wich viewcontroller is not released, overriding dealloc function: -(void)dealloc NSLog( @"class %@ -> deallocn", NSStringFromClass(self.class)); '
– Pablo Alegre
Nov 13 '18 at 12:56
add a comment |
Yes correct. That is exactly my problem. Unfortunately I still don't understand why I got retained references and I thought that maybe I can force close the VC so it will not use old objects anymore.
– progNewbie
Nov 13 '18 at 12:36
The typical case is a retained view controller property in the top level, that should be manually set to nil when it is dismissed. If everything is set to nil (try watch object variables debugging) and the problem persists you can also have some cross reference, something like a delegate declared as retained. You can also try to detect wich viewcontroller is not released, overriding dealloc function: -(void)dealloc NSLog( @"class %@ -> deallocn", NSStringFromClass(self.class)); '
– Pablo Alegre
Nov 13 '18 at 12:56
Yes correct. That is exactly my problem. Unfortunately I still don't understand why I got retained references and I thought that maybe I can force close the VC so it will not use old objects anymore.
– progNewbie
Nov 13 '18 at 12:36
Yes correct. That is exactly my problem. Unfortunately I still don't understand why I got retained references and I thought that maybe I can force close the VC so it will not use old objects anymore.
– progNewbie
Nov 13 '18 at 12:36
The typical case is a retained view controller property in the top level, that should be manually set to nil when it is dismissed. If everything is set to nil (try watch object variables debugging) and the problem persists you can also have some cross reference, something like a delegate declared as retained. You can also try to detect wich viewcontroller is not released, overriding dealloc function: -(void)dealloc NSLog( @"class %@ -> deallocn", NSStringFromClass(self.class)); '
– Pablo Alegre
Nov 13 '18 at 12:56
The typical case is a retained view controller property in the top level, that should be manually set to nil when it is dismissed. If everything is set to nil (try watch object variables debugging) and the problem persists you can also have some cross reference, something like a delegate declared as retained. You can also try to detect wich viewcontroller is not released, overriding dealloc function: -(void)dealloc NSLog( @"class %@ -> deallocn", NSStringFromClass(self.class)); '
– Pablo Alegre
Nov 13 '18 at 12:56
add a comment |
set AuthVC as your window's rootViewController.
let appDelegate = UIApplication.sharedApplication().delegate as! AppDelegate
instantiate AuthVC from storyboard and assign it to window's rootViewController
appDelegate.window?.rootViewController = AuthVC
answered Nov 13 '18 at 11:24
Viren MalhanViren Malhan
7515
you mean rootviewController of my NavigationController? Or do you meaninitial ViewController?
– progNewbie
Nov 13 '18 at 11:28
window's rootViewController. which is present in your app delegate. so your AuthVC will become first screen on window. then you can again continue with your normal navigation flow.
– Viren Malhan
Nov 13 '18 at 11:33
where in my AppDelegate do I set it as rootViewController?
– progNewbie
Nov 13 '18 at 11:36
i have updated my answer. set rootViewController to AVC on logout action.
– Viren Malhan
Nov 13 '18 at 11:57
My AppDelegate is in my Main.class. I set my AuthVC to rootviewcontroller there now. But this does not change anything. I need to do it when the logout button is pressed right? And do I even call dismissviewController anymore?
– progNewbie
Nov 13 '18 at 12:04
|
show 4 more comments
set AuthVC as your window's rootViewController.
let appDelegate = UIApplication.sharedApplication().delegate as! AppDelegate
instantiate AuthVC from storyboard and assign it to window's rootViewController
appDelegate.window?.rootViewController = AuthVC
answered Nov 13 '18 at 11:24
Viren MalhanViren Malhan
7515
you mean rootviewController of my NavigationController? Or do you meaninitial ViewController?
– progNewbie
Nov 13 '18 at 11:28
window's rootViewController. which is present in your app delegate. so your AuthVC will become first screen on window. then you can again continue with your normal navigation flow.
– Viren Malhan
Nov 13 '18 at 11:33
where in my AppDelegate do I set it as rootViewController?
– progNewbie
Nov 13 '18 at 11:36
i have updated my answer. set rootViewController to AVC on logout action.
– Viren Malhan
Nov 13 '18 at 11:57
My AppDelegate is in my Main.class. I set my AuthVC to rootviewcontroller there now. But this does not change anything. I need to do it when the logout button is pressed right? And do I even call dismissviewController anymore?
– progNewbie
Nov 13 '18 at 12:04
|
show 4 more comments
set AuthVC as your window's rootViewController.
let appDelegate = UIApplication.sharedApplication().delegate as! AppDelegate
instantiate AuthVC from storyboard and assign it to window's rootViewController
appDelegate.window?.rootViewController = AuthVC
answered Nov 13 '18 at 11:24
Viren MalhanViren Malhan
7515
set AuthVC as your window's rootViewController.
let appDelegate = UIApplication.sharedApplication().delegate as! AppDelegate
instantiate AuthVC from storyboard and assign it to window's rootViewController
appDelegate.window?.rootViewController = AuthVC
answered Nov 13 '18 at 11:24
Viren MalhanViren Malhan
7515
edited Nov 13 '18 at 11:55
answered Nov 13 '18 at 11:24
Viren MalhanViren Malhan
7515
answered Nov 13 '18 at 11:24
Viren MalhanViren Malhan
7515
answered Nov 13 '18 at 11:24
Viren MalhanViren Malhan
7515
7515
you mean rootviewController of my NavigationController? Or do you meaninitial ViewController?
– progNewbie
Nov 13 '18 at 11:28
window's rootViewController. which is present in your app delegate. so your AuthVC will become first screen on window. then you can again continue with your normal navigation flow.
– Viren Malhan
Nov 13 '18 at 11:33
where in my AppDelegate do I set it as rootViewController?
– progNewbie
Nov 13 '18 at 11:36
i have updated my answer. set rootViewController to AVC on logout action.
– Viren Malhan
Nov 13 '18 at 11:57
My AppDelegate is in my Main.class. I set my AuthVC to rootviewcontroller there now. But this does not change anything. I need to do it when the logout button is pressed right? And do I even call dismissviewController anymore?
– progNewbie
Nov 13 '18 at 12:04
|
show 4 more comments
you mean rootviewController of my NavigationController? Or do you meaninitial ViewController?
– progNewbie
Nov 13 '18 at 11:28
window's rootViewController. which is present in your app delegate. so your AuthVC will become first screen on window. then you can again continue with your normal navigation flow.
– Viren Malhan
Nov 13 '18 at 11:33
where in my AppDelegate do I set it as rootViewController?
– progNewbie
Nov 13 '18 at 11:36
i have updated my answer. set rootViewController to AVC on logout action.
– Viren Malhan
Nov 13 '18 at 11:57
My AppDelegate is in my Main.class. I set my AuthVC to rootviewcontroller there now. But this does not change anything. I need to do it when the logout button is pressed right? And do I even call dismissviewController anymore?
– progNewbie
Nov 13 '18 at 12:04
you mean rootviewController of my NavigationController? Or do you mean
initial ViewController?– progNewbie
Nov 13 '18 at 11:28
you mean rootviewController of my NavigationController? Or do you mean
initial ViewController?– progNewbie
Nov 13 '18 at 11:28
window's rootViewController. which is present in your app delegate. so your AuthVC will become first screen on window. then you can again continue with your normal navigation flow.
– Viren Malhan
Nov 13 '18 at 11:33
window's rootViewController. which is present in your app delegate. so your AuthVC will become first screen on window. then you can again continue with your normal navigation flow.
– Viren Malhan
Nov 13 '18 at 11:33
where in my AppDelegate do I set it as rootViewController?
– progNewbie
Nov 13 '18 at 11:36
where in my AppDelegate do I set it as rootViewController?
– progNewbie
Nov 13 '18 at 11:36
i have updated my answer. set rootViewController to AVC on logout action.
– Viren Malhan
Nov 13 '18 at 11:57
i have updated my answer. set rootViewController to AVC on logout action.
– Viren Malhan
Nov 13 '18 at 11:57
My AppDelegate is in my Main.class. I set my AuthVC to rootviewcontroller there now. But this does not change anything. I need to do it when the logout button is pressed right? And do I even call dismissviewController anymore?
– progNewbie
Nov 13 '18 at 12:04
My AppDelegate is in my Main.class. I set my AuthVC to rootviewcontroller there now. But this does not change anything. I need to do it when the logout button is pressed right? And do I even call dismissviewController anymore?
– progNewbie
Nov 13 '18 at 12:04
|
show 4 more comments
Or you can set root view controller for the window by next code in your settingsVC:
//Did tap logout button
self.view.window?.rootViewController = AuthVC
If it doesn't help you, please send how exactly you show NavigationViewController after AuthVC.
answered Nov 13 '18 at 11:51
GkoluniaGkolunia
828
I'd still need to call dismissViewController right?
– progNewbie
Nov 13 '18 at 12:08
add a comment |
Or you can set root view controller for the window by next code in your settingsVC:
//Did tap logout button
self.view.window?.rootViewController = AuthVC
If it doesn't help you, please send how exactly you show NavigationViewController after AuthVC.
answered Nov 13 '18 at 11:51
GkoluniaGkolunia
828
I'd still need to call dismissViewController right?
– progNewbie
Nov 13 '18 at 12:08
add a comment |
Or you can set root view controller for the window by next code in your settingsVC:
//Did tap logout button
self.view.window?.rootViewController = AuthVC
If it doesn't help you, please send how exactly you show NavigationViewController after AuthVC.
answered Nov 13 '18 at 11:51
GkoluniaGkolunia
828
Or you can set root view controller for the window by next code in your settingsVC:
//Did tap logout button
self.view.window?.rootViewController = AuthVC
If it doesn't help you, please send how exactly you show NavigationViewController after AuthVC.
answered Nov 13 '18 at 11:51
GkoluniaGkolunia
828
answered Nov 13 '18 at 11:51
GkoluniaGkolunia
828
answered Nov 13 '18 at 11:51
GkoluniaGkolunia
828
answered Nov 13 '18 at 11:51
GkoluniaGkolunia
828
828
I'd still need to call dismissViewController right?
– progNewbie
Nov 13 '18 at 12:08
add a comment |
I'd still need to call dismissViewController right?
– progNewbie
Nov 13 '18 at 12:08
I'd still need to call dismissViewController right?
– progNewbie
Nov 13 '18 at 12:08
I'd still need to call dismissViewController right?
– progNewbie
Nov 13 '18 at 12:08
add a comment |
Try this
let maiStoryBoard = UIStoryboard(name: "Main", bundle: nil) //Storyboard in which AuthVC lies
let authVC = mainStoryBoard.instantiateViewControllerWithIdentifier("AuthVC") as! AuthVC
let appDelegate = UIApplication.sharedApplication().delegate as! AppDelegate
appDelegate.window?.rootViewController = authVC
answered Nov 13 '18 at 13:03
SAIFSAIF
617
add a comment |
Try this
let maiStoryBoard = UIStoryboard(name: "Main", bundle: nil) //Storyboard in which AuthVC lies
let authVC = mainStoryBoard.instantiateViewControllerWithIdentifier("AuthVC") as! AuthVC
let appDelegate = UIApplication.sharedApplication().delegate as! AppDelegate
appDelegate.window?.rootViewController = authVC
answered Nov 13 '18 at 13:03
SAIFSAIF
617
add a comment |
Try this
let maiStoryBoard = UIStoryboard(name: "Main", bundle: nil) //Storyboard in which AuthVC lies
let authVC = mainStoryBoard.instantiateViewControllerWithIdentifier("AuthVC") as! AuthVC
let appDelegate = UIApplication.sharedApplication().delegate as! AppDelegate
appDelegate.window?.rootViewController = authVC
answered Nov 13 '18 at 13:03
SAIFSAIF
617
Try this
let maiStoryBoard = UIStoryboard(name: "Main", bundle: nil) //Storyboard in which AuthVC lies
let authVC = mainStoryBoard.instantiateViewControllerWithIdentifier("AuthVC") as! AuthVC
let appDelegate = UIApplication.sharedApplication().delegate as! AppDelegate
appDelegate.window?.rootViewController = authVC
answered Nov 13 '18 at 13:03
SAIFSAIF
617
answered Nov 13 '18 at 13:03
SAIFSAIF
617
answered Nov 13 '18 at 13:03
SAIFSAIF
617
answered Nov 13 '18 at 13:03
SAIFSAIF
617
617
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.
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%2f53279885%2fdismiss-all-views-from-navigationviewcontroller%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
You are presenting all
UIViewController's?– Sohil R. Memon
Nov 13 '18 at 12:01
The flow you have used sounds good to me, but I suspect a memory leak here which is keeping the objects alive.
– hardik parmar
Nov 13 '18 at 12:02