New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
App-switcher closes when closing TextSecure #1037
Comments
This is the consequence of a workaround for an Android OS bug that was causing TextSecure to miss incoming messages after swiping from the recent tasks list. I agree it's unfortunate, but it's better than the alternative, and I don't think there's anything we can do until Android fixes their bug. |
Could you please point me to the code that you used for working around that bug? |
I guess it's this: b5fe378 |
Is this bug still present in Android 5, 5.1 and 6? |
@sedrubal looks like it's back. Can reproduce if closing the unlocked Signal 😕 |
Obviously. 😴 |
Has the root cause bug in Android been fixed? None of the other messengers have this really annoying problem. |
I am not an Android developer but reading the @Override
public void onReceive(Context context, Intent intent) {
String data = ...
ApplicationContext.getInstance(context)
.getJobManager()
.add(new PushContentReceiveJob(context, data));
} because the execution of your If instead you invoked an @Override
public void onReceive(Context context, Intent intent) {
String data = ...
Intent service = new Intent(context, PushContentReceiveService.class); // PushContentReceiveService currently doesn't exist
Bundle extras = new Bundle();
extras.putString("data", data);
service.setExtras(extras)
startWakefulService(context, service);
} Again, not an Android developer, but what is the advantage of using a selfmade |
This behavior still exists in Android 7.0 and remains mildly annoying. Has anyone looked at @nils-werner's comment? |
@Raindeer44 I think that comment is unrelated to this issue. I honestly can't remember how this was originally manifesting, but I think it was through SMS messages. Maybe this wouldn't apply to people who aren't using Signal for SMS. Someone would have to disable this workaround and test all the different scenarios. |
Still a problem in 8.1. It would be nice to find a better alternative. |
This issue should NOT be closed. I have tested this behavior using Signal without SMS integration and with SMS integration, behavior occurs in either mode. Action/Cause:
Result/Effect:
Consider this 'Unexpected Behavior' because no other Application I have ever used, when closed via the Recents screen, causes the entire Recents Screen to also close. This interrupts the normal behavior/ability to quickly close other Apps or switch to another App. Additional Details/Troubleshooting:
Phone: Pixel XL Description of Android's "Recents" Screen if that Term is unclear: Similar behavior reported by multiple Signal Users on this site and others. Searched Signal's Support Center website using same terms/strings used to locate this issue/page but Signal's Support Center portal kept returning "No results found". No option to Submit this feedback through the App so posting here. |
I am unable to reproduce this issue on Android P, fwiw. It's still occurring consistently on older OS levels (8.1 for example). |
Issue still occurs for me. Android Oreo, pixel 2. It's rather annoying |
Still experiencing this on Android Oreo 8.0.0, Samsung Galaxy Note 8. |
If it's any consolation, it's fixed in Android 9.0. Apps are no longer allowed to close all the cards like this (thank god) |
When closing the Textsecure app from the default app-switcher (see screenshot) it also closes the app-switcher itself unlike if i close other apps from the app-switcher.
I'm using Cyanogenmod-Version 11-20140210-SNAPSHOT-M3-mako, my TextSecure is up-to-date.
Although it is not a big issue, it is annoying (might annoy others too) and i think it might lead to other errors.
The following screenshot was taken right before closing Textsecure by swiping from left to right. After that, the app-switcher closes.
The text was updated successfully, but these errors were encountered: