Currently if the user refreshes the page while on a page that requires auth, they are shown an error when the page reloads. This is because on page load the user is not actually logged until a few seconds later. The Google Auth process doesn't start until after the page has finished loading (which is expected).
Better behavior would be to redirect the user to the homepage (which happens now) and not show the error. Any time a user loads the page from scratch at http://tweet.crc.io/#!/tweet or /#!/scheduled, we should redirect the user to the homepage and not show an error.
Currently if the user refreshes the page while on a page that requires auth, they are shown an error when the page reloads. This is because on page load the user is not actually logged until a few seconds later. The Google Auth process doesn't start until after the page has finished loading (which is expected).
Better behavior would be to redirect the user to the homepage (which happens now) and not show the error. Any time a user loads the page from scratch at http://tweet.crc.io/#!/tweet or /#!/scheduled, we should redirect the user to the homepage and not show an error.