signalapp / signalapp/Signal-Android
Signal Crashes Upon Entering a previously established Chat. It's Unusable.
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 29.4k
- Forks
- 6.9k
- PR merge metrics
- No merged PRs in 30d
Description
- I have searched open and closed issues for duplicates
- [X ] I am submitting a bug report for existing functionality that does not work as intended
- [ X] 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
Clean install (no import from previous account). Then I add a single contact. Send a message to said contact. I exit the application when I try to go back in my initials (in my user) have changed from AA to +2. Any attempt to set my name and lastname (fields show up as empty) will not work. If I try to go back to the chat that I created, then the application crashes.
If enable airplane mode, the application works. It will inmediately crash if I'm in a chat when I disable airplane mode.
Steps to reproduce
- Create a new account.
- Chat with a single person. ONe message. And move out of the application
- Attempt to go back to the chat.
Actual result: The appliacation crashes
Expected result: The application shouldn't crash.-
Device info
Device: Motorola G9 Plus
Android version: 11
Signal version: 5.44.5
Link to debug log
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 reproducing the crash when reopening the established chat or disabling airplane mode on the listed Android setup. Trace the crash from chat entry and network-state changes; done means the chat opens and remains usable without crashing in both online and offline transitions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100