Cannot unlock app as no passphrase was set before locking

[deshant]

• I have searched open and closed issues for duplicates
• I am submitting a bug report for existing functionality that does not work as intended
• I have read https://github.com/signalapp/Signal-Android/wiki/Submitting-useful-bug-reports
• This isn't a feature request or a discussion topic

---

Bug description

A new user, just downloaded the app, registered myself. Now I am locked out of the app and can't unlock. I have clicked on "lock signal" from notification bar, and cannot unlock. I had not set any passphrase after registration.

Steps to reproduce

• Fresh registration
• Do not setup any PIN or passphrase or go to any settings even.
• Send a text to someone. (mentioning this as I did this, else I don't this this matters)
• Notification starts appearing that Signal is unlocked.
• Lock it from notification
• Can't unlock using device PIN or even after setting passphrase in device security settings.

Actual result: Cannot unlock app using device PIN or passphrase. No PIN or passphrase was set in Signal app.
Expected result: Should be able to unlock using device PIN or passphrase.

Device info

Manufacturer : Motorola
Model : Motorola one power
Android version: 10 (8f02e, QPTS30.61-18-16-3)
Signal version: 5.0.8

Link to debug log

https://debuglogs.org/ba84dc270117d72705c1da4ac122c73666c01453efafb9b09ff23472fe4f138c

Comments

I have fingerprint unlock enabled. I know it is not used by signal but I was expecting my PIN to be accepted since I have not explicitly set any from the app after installing.
If no separate unlocking mechanism is set in app, then either the app should let user set it first before locking them out or let the device PIN or passphrase work.

[bme13]

Hi @deshant and welcome,
To me it seems you enabled the screen lock. This should use the device fingerprint method to unlock.

[theprojectsomething]

Same issue. There is no fingerprint option available, only passphrase which hasn't been set. No way around it.

[endercrest]

I am having a similar problem. Restarted phone and is now prompting for a passphrase to unlock. I never used the lock notification.

[deshant]

Hi @deshant and welcome,
To me it seems you enabled the screen lock. This should use the device fingerprint method to unlock.

Nothing happens when I put my finger on fingerprint scanner. Not able to unlock in any way possible.

[theprojectsomething]

Some more context - I had the app installed (but unused) and updating in the background for some time (possibly across phones). All phones had a fingerprint sensor. Joining the beta program had no effect. Deleting the app completely (losing my conversations) and reinstalling resolved the issue.

[deshant]

@theprojectsomething This is barely a workaround, can't accept it as a solution. The app is having a bug which is locking users out. Let's hope some contributor picks this up.

Meanwhile I am keeping the app as it is, so that if someone fixes it I can test the new update. There is only 1 test message from my friend so nothing to lose here.

[theprojectsomething]

@deshant apologies, I needed to continue using the app which was why I opted for the nuclear option ... definitely wasn't suggesting deleting as a useful workaround - just providing context for any potential deep-dig.

Looks like beta channel is only a few patches behind master (I'm currently running a 4 day old build), so here's hoping your persistence pays off (pre whatsappageddon)!

[lewiji]

Same issue, except my phone (Pixel 4) doesn't have a fingerprint reader, and I use face unlock.

From reading the documentation it looks like my phone's PIN should unlock but it doesn't. I have also tried disabling face unlock, leaving only the PIN option, clearing cache and restarting the phone.

[greyson-signal]

@deshant I think I see one possible problem in your debuglog where we don't properly do the initialization we're supposed to do after your first-ever app launch. I put some failsafes in the upcoming 5.2.x.

If anyone else sees this again, please take a debuglog asap and share it here, thank you!

[deshant]

@theprojectsomething Hey its fine, I was only pointing out that resetting app is not a solution to avoid any misunderstanding. You need to continue using the app, or else you would also have helped in re-testing from scratch, since you have anyways sacrificed your messages.

@greyson-signal Glad the logs could help. Please help clear my understanding of the fix.

@deshant I think I see one possible problem in your debuglog where we don't properly do the initialization we're supposed to do after your first-ever app launch. I put some failsafes in the upcoming 5.2.x.

Correct me if I am wrong here, the fix will now properly initialize for first-ever app launch and this issue will not occur. This means for cases like me (already locked out), even if I upgrade to the build with the fix, I will still be locked out as the fix only works for initial launches.

If I am right here, I will have to nuke the app just like @theprojectsomething did.

[c-rizz]

@deshant I think I see one possible problem in your debuglog where we don't properly do the initialization we're supposed to do after your first-ever app launch. I put some failsafes in the upcoming 5.2.x.

If anyone else sees this again, please take a debuglog asap and share it here, thank you!

I belive I'm having the same issue. A few days ago I reinstalled signal after a long time I haven't used it, now I'm locked out of the app. It says "Signal is locked" and requires a "passphrase". I don't remember setting it. Two questions:

• Is it a signal passphrase or is it supposed to be the android unlock?
• Will the failsafes you mentioned allow to see currently unread messages or do they still require a reinstall?

I'm attaching a debug log

Thanks!

https://debuglogs.org/c89f6b83b2ba58309a12f2d5770ab835566d20e55a4ad9576c38fc7472b73907

[mulmschneider]

Encountered the same issue. Also had the app installed for a long time, but wasn't using it. Completed initial setup yesterday, and then pressed 'lock' (without setting any kind of passphrase).

Logs: https://debuglogs.org/c47853c7e23dc1871e04d39cc2d98459e59937afe7f43ea379b1e15861ff7946
Note: I updated to the latest version in the app-store after hitting the passphrase screen, but before generating the logs.

[greyson-signal]

@deshant I believe the best course of action would be to reinstall the app, yes. There's actually a bunch of less-visible state that probably is also screwed up besides this particular flag. I'm sorry :( I'm guessing you haven't been able to use the app for the past 5 days though?

The other users who are describing scenarios where they installed the app a long time ago but just opened it for the first time makes more sense to me why this may happen, but I find your scenario (where you downloaded and opened soon after) more confusing. Do you recall doing anything else of note?

[rboyer]

This just happened to me as well on my old Moto X test phone on Android 5.1 (very recently installed with no backup restored):

https://debuglogs.org/1144aa2430498b069d6c6d1fa55952b1a71ce3c8cc2b6ab62acd0d729ab6c7b9

[c-rizz]

@deshant I believe the best course of action would be to reinstall the app, yes. There's actually a bunch of less-visible state that probably is also screwed up besides this particular flag. I'm sorry :( I'm guessing you haven't been able to use the app for the past 5 days though?

The other users who are describing scenarios where they installed the app a long time ago but just opened it for the first time makes more sense to me why this may happen, but I find your scenario (where you downloaded and opened soon after) more confusing. Do you recall doing anything else of note?

I belive I installed it on the 11th, used it a bit, then didn't use it until today when I tried to open it.
Also, I'm not sure if this is helpful, the precise error it gives is "Invalid passphrase!"