-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Contact names won't sync. #1428
Comments
I'm finding that contacts will go from having their contact recognized to unrecognized after exchanging messages. I don't know how to reliably reproduce the issue though. Pinging @nitrocalcite - I know that you've had this issue more than I have - can you list exact steps to reproduce plus a debug log? |
I have the exact same issue now, as soon as I get new messages from a contact, the contact name is gone and the phone number is shown and the contact color is grey. OS: Arch Linux |
+1 |
Hey everyone. A couple things would help us track this down:
And a question for all of you: is it just one or two contacts this is happening with? Or all of them? |
Changing the color on Android immediately changed the color (and brought back the correct name) on desktop. As did things like changing the group name. Unfortunately it's happening with quite a few contacts & groups so it'd be great to not have to edit each one on Android if possible. I've seen it with 1 contact with a normal name (no special chars), and 1 group with an ampersand. |
Something changed in the last couple of days, and I too also have this issue. This is duplicated across Windows 10, OSX, Linux Mint. Also changing the color does force an update to render the name. So, I will use the workaround for now. Just wanted to chime in that I also experience this issue. |
This should help us track down the source of disappearing conversation names, as seen in #1428. // FREEBIE
In the PR above I've attempted to add some logging to debug where this change is happening. So far I haven't gotten it to repro locally. In addition to Scott's list above, could you tell us a bit about the state of the app at the time these names are lost? For instance, at the time of the change:
|
I also have the same problem. |
Okay, I believe I understand the core reason for this behavior - receiving messages when the app is 'in the background' in the Chrome App sense. So likely when it's either not visible or you haven't interacted with it lately. Working on a fix now. |
A recent change to fetch conversations less didn't take into account all that can happen in the app without the inbox loaded. That only happens when the window is shown, and messages can come in with the app in the background. In that case, the conversation wouldn't have been loaded from the database, but would be saved to the database anyway, losing data. This change fetches all conversations as soon as the the data store is ready for a fetch. It also introduces failsafe throws to ensure that synchronous ConversationController accesses don't happen until the initial fetch is complete. A new getUnsafe() method was required to account for some of the model setup that happens during that initial conversation fetch. Fixes #1428 FREEBIE
* Fetch all conversations on startup of app, not on inbox load A recent change to fetch conversations less didn't take into account all that can happen in the app without the inbox loaded. That only happens when the window is shown, and messages can come in with the app in the background. In that case, the conversation wouldn't have been loaded from the database, but would be saved to the database anyway, losing data. This change fetches all conversations as soon as the the data store is ready for a fetch. It also introduces failsafe throws to ensure that synchronous ConversationController accesses don't happen until the initial fetch is complete. A new getUnsafe() method was required to account for some of the model setup that happens during that initial conversation fetch. Fixes #1428 FREEBIE * Fix tests: ConversationController.load() required before get() FREEBIE
Hello, I also had this problem. The workaround (change color of contact on android) helped, but what can I do with groups? I cant change goup color (there is no group color it is composed of persons color). My group on Desktop are remaining without name called "Unknown Group". |
You can click Settings in the main triple-dot menu (in the top-middle), then click Import Now at the bottom to request all the latest contact/group information from your phone. |
@scottnonnenberg Thanks, that solved the problem for me. |
Bug description
Signal desktop won't sync this contact's name. They have Signal and their name has appeared before. As you can see, it defaults to the phone number/grey style. This has happened with one other contact and seems to occur when I restart the computer. I have reinstalled Signal Desktop three times. Each time this happens I have to manually import contacts again. Perhaps, on launch, Signal should auto import just to be safe?
Steps to reproduce
Actual result: The contact's name is not recognized. It defaults to the phone number and gray color.
Expected result: The contact name should sync and each contact should be color coded rather than the default gray.
Screenshots
Platform info
Operating System: Windows 10
Browser: Chrome 60.0.3112.113
Signal version: 0.43.2
Link to debug log
https://gist.github.com/0c58f9b93f145382bebf538d14531359
The text was updated successfully, but these errors were encountered: