signalapp / signalapp/Signal-Android
Registration in Slovenia often fails
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
In recent months most of Slovenian mobile operators started using SMS filtering.
Result: new users of Signal (or existing that want to change phone) are unable to register. I have several reports from users using different mobile carriers, that they do not receive SMS. But they do not have an option to receive robocall neither.
So sever of them just moved to Viber, which is bad.
My question: could you enable robocall or some ternative method for registration?
Screenshots
No response
Device
Varoois devices
Android version
Various
Signal version
Latest
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 reviewing the Android registration flow and the reports in the issue comments, especially the different Slovenian carriers and the lack of received SMS. No implementation file or test is identified in the issue. Done would require an agreed registration change that addresses the reported failure and is verified for the affected scenarios.
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
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100