Ok, makes sense!

--
tifi.-


On 21 July 2013 12:54, Maxi Rosson <notifications@github.com> wrote:

> In jdroid-android/src/main/java/com/jdroid/android/ActivityLauncher.java:
>
> >  	public static void launchActivityClearTask(Class<? extends Activity> targetActivityClass,
> >  			Boolean requiresAuthentication) {
> >  		Activity currentActivity = AbstractApplication.get().getCurrentActivity();
> >  		Intent intent = new Intent(AbstractApplication.get(), targetActivityClass);
> >  		intent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
> > -		if (AndroidUtils.isPreHoneycomb()) {
> > -			ClearTaskIntent.execute(true);
> > -		} else {
> > -			intent.addFlags(Intent.FLAG_ACTIVITY_CLEAR_TASK);
>
> It wasn't working as expected. In some scenarios, after opening the app
> from the recents screen, the login screen was displayed when the user was
> logged. So I decided to use the broadcast receiver approach for all
> versions.
> … <#14001f0d48c868cc_>
> On Jul 21, 2013 12:22 PM, "Estefanía Caravatti" <notifications@github.com>
> wrote: In
> jdroid-android/src/main/java/com/jdroid/android/ActivityLauncher.java: >
> public static void launchActivityClearTask(Class<? extends Activity>
> targetActivityClass, > Boolean requiresAuthentication) { > Activity
> currentActivity = AbstractApplication.get().getCurrentActivity(); > Intent
> intent = new Intent(AbstractApplication.get(), targetActivityClass); >
> intent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK); > - if
> (AndroidUtils.isPreHoneycomb()) { > - ClearTaskIntent.execute(true); > - }
> else { > - intent.addFlags(Intent.FLAG_ACTIVITY_CLEAR_TASK); Is there any
> particular reason to stop using Intent.FLAG_ACTIVITY_CLEAR_TASK on versions
> that support it? — Reply to this email directly or view it on GitHub<
> https://github.com/maxirosson/jdroid/pull/72/files#r5309335> .
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/maxirosson/jdroid/pull/72/files#r5309406>
> .
>