Ahh OK, I understand now. I think it would be better to do it this way:
Have a Splash Screen Activity as you have now. Make a BaseActivity, which keeps some functionality which checks whether you are logged in or not and have all your Activities implement that. So when you are not logged in it starts the Log In Activity and forces a user to log in. This eliminates the need of calling Finish on your Splash Screen Activity which most likely is causing you this trouble. Does this make sense? On Thu, Jan 12, 2012 at 12:28 PM, devbuzz <de...@fieldmetrix.com> wrote: > I removed the noHistory option because I'm using the SplashActivity as a kind > of initial workflow processor. > > So if the user has already logged in before they get: > SplashActivity -> Login Screen-> SplashActivity.OnActivityResult -> Home > Screen > > If this is the first time they are logging in they get: > SplashActivity -> Auth Screen -> SplashActivity.OnActivityResult -> Login > Screen-> SplashActivity.OnActivityResult -> Home Screen > > So I can't use noHistory because I need SplashActivity to process > OnActivityResult. > > -- > View this message in context: > http://mono-for-android.1047100.n5.nabble.com/SplashActivity-and-single-instance-tp5138098p5139699.html > Sent from the Mono for Android mailing list archive at Nabble.com. > _______________________________________________ > Monodroid mailing list > Monodroid@lists.ximian.com > > UNSUBSCRIBE INFORMATION: > http://lists.ximian.com/mailman/listinfo/monodroid -- Med Venlig Hilsen / With Best Regards Tomasz Cielecki http://ostebaronen.dk _______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
