renegens
commented
8 years ago ok after some diggin I found the solution which what pretty obvious in fact but in case anyone is wondering how check this below.
/**
- Activity that starts ParseLoginActivity if the user is not logged in.
- Otherwise, it starts the subclass-defined target activity.
- To use this, you should subclass this activity and implement
- {@link ParseLoginDispatchActivity#getTargetClass} to return the class of the
- target activity that should be launched after login succeeds. If the user
- cancels the login, your app will go back to whatever activity it was on before
- your subclass dispatch activity was launched, or exit the app if your subclass
- is the first activity in your app's backstack.
- You can think of your subclass as a gate keeper for any activities that
- require a logged-in user to function. You should have one gate keeper per
- entry path into your app (e.g. launching the app, or entering through push
- notifications). When your app launches or receives a push notification, you
- should specify that your gate keeper activity be launched (and the gate
- keeper will redirect to your target activity upon successful login). */
taken from ParseLoginDispatchActivity.java
Hello,
I am currently implementing the ParseLoginBuilder on an Activity called LoginActivity which builds the signup or login proccess and then calls onStart with an intent to launch the activity for the main user called MainActivity.
The problem lies that when I log out the user and return to the ParseLoginActivity, then press the back button the fragment goes away but the underlying screen is revealed which is the empty activity that hosts the ParseLoginBuilder.
So my question is there away to launch directly the Builder from the appdrawer with checking if the user is logged in?