signalapp / signalapp/Signal-Android
New user registration broken even with VPN in high-risk countries with anti-signal blocks
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 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
Attempting to register from a country where Signal is blocked is almost impossible even with a working VPN EVEN IF not using local number (e.g. using a Google Voice acc)
Without VPN obviously nothing works, but with VPN the process never reaches the stage where confirmation SMS is sent
Again, I understand the hardship but it would be very nice if something could be done about these issues since people in these countries often are most needing a good secure comms solution
Screenshots
No response
Device
No response
Android version
No response
Signal version
No response
Link to debug log
No response
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 reproducing registration from an affected high-risk country with and without a VPN, using a non-local number. Gather the missing device, Android, Signal version, and debug-log details, then trace where the flow stops before the confirmation SMS; done means registration reaches SMS confirmation under the described conditions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100