Always asking for log in after killing the app and opening(not storing authorized state)
See original GitHub issueHi, In your android sample after log in successful it is directing to Token activity. But when I close the app and open again it is again asking for log in. Following condition is always failing. I checking in your sdk it is maintaining state in shared pref but why it is not working.
if (mAuthStateManager.getCurrent().isAuthorized() && !mConfiguration.hasConfigurationChanged()) { Log.i(TAG, "User is already authenticated, proceeding to token activity"); startActivity(new Intent(this, TokenActivity.class)); finish(); return; }
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
How to keep android applications always be logged in state?
This depends on the actual server - side implementation of that form. But remember: This is an security issue. So never store authorization...
Read more >Authentication Required window stuck after login - Ask Ubuntu
press Alt + F2 , type r then Enter. or. in terminal, type killall -3 gnome-shell. This should just restart Gnome Shell. You...
Read more >iPhone keeps asking for Apple ID password
Either way, select Always Require at the top, authenticate if it asks, then select Require After 15 Minutes. And then authenticate again.
Read more >Salesforce CLI: auth web login issue
I properly installed CLI. In a command window, I enter: sfdx force:auth:web:login -d -a DevHub in order to log in to the trial...
Read more >Force stop and clear cache: Here's what you need to know
After the app has been killed, the next step is to delete the data in the cache directory. When an application needs a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@tikurahul I think @prashanthd means that the demo app is not correctly handling saved state. This is likely a bug in the demo app; I’ll investigate when I get some time.
Fix is merged; closing this.