I have:
Related to #7475 and #7474
The Signal pattern unlock screen is displaying on top of the Android pattern unlock screen. Under certain screen timeout conditions described below, on waking an Android device the Signal unlock screen will display instead of the Android unlock screen and will sometimes remain displayed after inputting correct unlock pattern. If you then input your pattern into the Signal unlock screen, the Android unlock screen will display. After then unlocking your Android as usual, the Signal app will still require you to input the unlock pattern to unlock Signal.
Actual result: Signal unlock screen is displayed before the Android unlock screen. Entering pattern does not immediately unlock Signal.
Expected result: Android lock screen is displayed and Signal unlock screen is only displayed when you enter Signal.
None as of now because android studio is a resource hog.
Device: Nexus 6
Android version: 7.0.0
Signal version: 4.17.0
https://debuglogs.org/774c5c5af6648b2e279f7f884813d348d27a00817c05a7485b9ef42fcbfa20f7
That's super weird, I tried it on an N device and couldn't reproduce. The unlock screen is Android-provided, and seems kinda flaky. Might just remove it in favor of fingerprint-only.
Then what do you do on a device without a fingerprint scanner (or one where it is not configured)? Revert to the old password, that disappears from the settings once you choose a pattern unlock?
I'm using Moto G4 with Nougat 7.0.1 and I'm experiencing this as well. The Signal lock screen is sometimes on top of the Android lock screen, which for some reason means that I have to unlock the Signal lock screen, then the Android lock screen, then the Signal lock screen again.
Here's how to reproduce:
Will hook you up with a debug log next time it happens!
It doesn't seem that there's any further action I can take here, please reopen if anyone sees a workaround.
This particular issue with the Signal lock screen seems to have been resolved and I can no longer reproduce.
I still experience the problem.
I haven't experienced it for quite some time, but sadly there doesn't seem to be anything Moxie can do about it. Perhaps one day, Google will get their asses out of their civilian monitoring stations and release a way to fix this.
Well, without this wanting to sound confrontational and conceding that Google's lockscreen API is at fault here, this still is a regression in Signal, since this only apperead after the old lock screen disappeared.
Most helpful comment
Then what do you do on a device without a fingerprint scanner (or one where it is not configured)? Revert to the old password, that disappears from the settings once you choose a pattern unlock?