signalapp
Contact search for discoverable contact: multiple versions of the same contact appear and all report that the user has stopped using Signal
Guidelines
- [X] I have searched searched open and closed issues for duplicates
- [X] I am submitting a bug report for existing functionality that does not work as intended
- [X] This isn't a feature request or a discussion topic
Bug description
I installed Signal for the first time. So did my friend. Initially each of us made ourselves undiscoverable. Then each set ourselves to be discoverable. The result is that neither of us can connect with the other. On my end - I am unsure presently about my friend's - I see three contact results for her, but each of them declares that she has stopped using Signal. I rebooted my phone to no avail. I found the problem described on Reddit.
I am surprised that no bug report exists already for this problem. If widespread this problem will decimate sign-ups.
Screenshots
No response
Device
Asus Zenfone 8
Android version
Android 13
Signal version
7.28.4
Link to debug log
https://debuglogs.org/android/7.28.4/920684c8dc2adb297f9fc87e029856f17200e57fb5630df9985854813ab14318
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
@jeffrey-signal : you are welcome. Will someone actually investigate the report, or is the situation the following absurd one? Someone reports a bug. No-one attends to the report. The bot closes the report. The reporter re-opens it. Rinse and repeat.
@LinuxOnTheDesktop this issue is labeled as acknowledged, so it won't be closed by the bot.