signalapp / signalapp/Signal-Android
Locked out of account Reglock'd!
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 29.4k
- Forks
- 6.9k
- PR merge metrics
- No merged PRs in 30d
Description
Guidelines
- I have searched open and closed issues for duplicates
- I am submitting a bug report for existing functionality that does not work as intended
- This isn't a feature request or a discussion topic
Bug description
Yesterday, I attempted to reset my phone. I tried to log into signal. My account does have a registration pin. I went through to the part until it requests a PIN. I entered that and saw a small toast notification saying "Reg lock!" and then it just spins indefinitely. This happened yesterday. I found some old issue saying that the user was probably rate limited and needed to wait 24 hours. I have now waited over 24 hours and tried again and I'm stuck in the same hell cycle. I can't read very important business emails in my signal account. I appear to just be fully locked out. I've tried several times, reset my cache and storage (as well as uninstalled and reinstalled the app). I'm 100% sure I am entering my pin correctly (copy and pasted from my password manager and I've used this pin many times in the past to re-register). Here's the debug log:
Screenshots
No response
Device
Pixel 9 XL
Android version
16
Signal version
8.9.1
Link to debug log
https://debuglogs.org/android/8.9.1/5f7fdd6fae437a6464fab5cbae53de600084eb2e1b29b6b61d4a5adb46e69cb0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked debug log and the registration details in the issue, then reproduce the PIN entry flow on a Pixel 9 XL running Android 16 with Signal 8.9.1. Trace the Reglock path to determine why a valid PIN leaves registration spinning. Done means the registration outcome is handled correctly instead of leaving the user stuck.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100