Thank you for clarifying the app's page memory and how it works. But when I set the "loginPage" as the startpage and users login with onSuccess navigate to homePage 'useFullRefresh' this homePage is NOT becoming the new "first page". When I close down the app and reopen it, no matter what, it ALWAYS launches to the "loginPage".
So, if I want to change this behavior as you suggested here;
"If you don't want this behavior you should implement your own logic. For example, you can remember credentials in localstorage variable and use it after first login and send it automatically after first login"
Maybe there is another workaround..
I've set my HomePage as the "startpage" in app settings. On my homePage I need to set TWO buttons. 1.Login and 2.Logout.
As a first time app user, the login button (navigates to the loginPage) would ONLY be visible and the logout button invisible. Once the user either logs in or registers, their sessionToken & UserID are mapped into local storage, and they navigate back to the homePage.
Here is where things get problematic with this workaround... How do I make the loginButton ONLY visible when nothing is stored in Local Storage and how do I make the logoutButton ONLY visible (and loginButton invisible) when a userSession is stored in Local Storage?
This logic would make more sense as oppose to setting start pages and app page memory page full refresh. No?