Databases
StackOverflow2013
Postsdbo
POLogout from the application Android
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POLogout from the application Android
    primarykey
    data
    text
    <p>I have tried to logout from my app when the user clicks on Logout.It is working fine in case the user after login without closing the app if he doed logout .Then it is working properly.Back button will be ineffective in case to show again the login page after doing login But when the user after login closes the application and then he does logout the login page is not showing it is showing a blank page to me </p> <p><strong>Code</strong> </p> <pre><code>public class AppState { private static AppState singleInstance; private boolean isLoggingOut; private AppState() { } public static AppState getSingleInstance() { if (singleInstance == null) { singleInstance = new AppState(); } return singleInstance; } public boolean isLoggingOut() { return isLoggingOut; } public void setLoggingOut(boolean isLoggingOut) { this.isLoggingOut = isLoggingOut; } } </code></pre> <p><strong>OnClick of logout</strong></p> <pre><code>logout.setOnClickListener(new OnClickListener() { @Override public void onClick(View arg0) { SharedPreferences myPrefs = getSharedPreferences("MY", MODE_PRIVATE); SharedPreferences.Editor editor = myPrefs.edit(); editor.clear(); editor.commit(); AppState.getSingleInstance().setLoggingOut(true); Log.d(TAG, "Now log out and start the activity login"); Intent intent = new Intent(HomePage.this, LoginPage.class); intent.setFlags(Intent.FLAG_ACTIVITY_CLEAR_TOP); startActivity(intent); } }); </code></pre> <p><strong>IN the LoginActivity</strong></p> <pre><code>protected void onActivityResult(int requestCode, int resultCode, Intent data) { if (requestCode == MAIN_ACTIVITY_REQUEST_CODE) { if (!AppState.getSingleInstance().isLoggingOut()) { finish(); } else { AppState.getSingleInstance().setLoggingOut(false); super.onActivityResult(requestCode, resultCode, data); } } else { super.onActivityResult(requestCode, resultCode, data); } } @Override protected void onNewIntent(Intent intent) { super.onNewIntent(intent); } </code></pre> <p>Please suggest me what i have done wrong in this</p> <p>After Your Suggestions of <strong>Vivek Bhusal</strong> i tried to use sharedpref </p> <p><strong>HomePage logout Clicked</strong></p> <pre><code>logout.setOnClickListener(new OnClickListener() { @Override public void onClick(View arg0) { SharedPreferences myPrefs = getSharedPreferences("Activity", MODE_PRIVATE); SharedPreferences.Editor editor = myPrefs.edit(); editor.clear(); editor.commit(); //AppState.getSingleInstance().setLoggingOut(true); setLoginState(true); Log.d(TAG, "Now log out and start the activity login"); Intent intent = new Intent(HomePage.this, LoginPage.class); intent.setFlags(Intent.FLAG_ACTIVITY_CLEAR_TOP); startActivity(intent); } }); private void setLoginState(boolean status) { SharedPreferences sp = getSharedPreferences("LoginState", MODE_PRIVATE); SharedPreferences.Editor ed = sp.edit(); ed.putBoolean("setLoggingOut", status); ed.commit(); } </code></pre> <p>On the <strong>Login Page</strong></p> <pre><code>protected void onActivityResult(int requestCode, int resultCode, Intent data) { SharedPreferences sp = getSharedPreferences("LoginState", MODE_PRIVATE); boolean stateValue = sp.getBoolean("setLoggingOut", false); if (requestCode == MAIN_ACTIVITY_REQUEST_CODE) { if (!stateValue) { finish(); } else { //AppState.getSingleInstance().setLoggingOut(false); updateLoginState(false); super.onActivityResult(requestCode, resultCode, data); } } else { super.onActivityResult(requestCode, resultCode, data); } } </code></pre> <p>Still the same issue showing a blank screen when i again restart the app and then do the logout.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDeveloper
    1. USDeveloper
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POLogout from the application Android
      1. USDeveloper
      1. VTBountyStart
    2. VO
      singulars
      1. POLogout from the application Android
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POLogout from the application Android
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI didn't understand if the LoginActivity is always show (like a splash screen), even if user has already logged in. Or is it skipped?
      singulars
      1. POLogout from the application Android
      1. USJJ86
    2. CO@JaAd if the user does the login at first time and at the same time he does i am able to show the login page.but if the user loged in the application and closes the application then again starts the app and then he is closing the app then it is showing a blank activity it is not showing the login page
      singulars
      1. POLogout from the application Android
      1. USDeveloper
    3. COSorry but may be silly to ask you, but why are you listening to OnActivityResult in Login Activity. Because to me it looks like you are starting a new Intent after logout
      singulars
      1. POLogout from the application Android
      1. USthe100rabh
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload