-
-
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
Every Disappearing Message Sent on Signal iOS Received Twice on Signal Desktop on Mac #1138
Every Disappearing Message Sent on Signal iOS Received Twice on Signal Desktop on Mac #1138
Comments
Can you submit the iOS debug log too?
… On Apr 28, 2017, at 20:22, Xander Dunn ***@***.***> wrote:
I have searched open and closed issues for duplicates
Bug description
Steps to reproduce
Send a message on Signal iOS. Signal is not open on Desktop
Open Signal on Desktop
Actual result: Every message that was sent by myself on Signal iOS is received twice on Signal Desktop.
Expected result: Every message should be received only once on Desktop.
Screenshots
What I sent on Signal iOS:
Signal Desktop receiving everything twice:
Platform info
iOS: 10.3.1
Mac Browser: Google Chrome 58.0.3029.81
Desktop Signal version: 0.37.0
iOS Signal Version: 2.10.1
Link to debug log
Desktop: https://gist.github.com/4daf45818c79d54d27ba77dfce37f8e6
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
iOS Signal now version 2.11.1 Desktop: https://gist.github.com/92256a1c3453d7a897fcdc0ded0c161c |
@xanderdunn What if you turn off disappearing messages? |
@liliakai It looks like turning off disappearing messages made the messages appear only once on desktop. Turning it back on, it eventually came back. I didn't try more than 3 test messages, so not very scientific. |
Thanks. That's enough to hint that this is related to disappearing messages on the desktop side. Most likely a race between saving the message initially and then immediately updating it to start the countdown timer. |
Same as #1038? |
Not the same. |
This also happens in messages sent from Signal on Android. |
And, it happens with me using Signal Android when I have Signal Desktop online - not just offline. Also, often one of the duplicates has a single "sent" checkmark, not the duplicate return receipt checkmark. I do wonder if #1038 is somehow related. I'll try to do some rigorous testing in the next few days, this is happening almost constantly with me. |
@gordon-morehouse very unlikely. #1038 is about hiding group messages that were duplicated because of network failures, you are experiencing something else (or your messages fail once every time). |
Okay, I got this to happen in a short span of time as shown in the screenshot from Desktop, and here are debug logs on both platforms. Relevant phone number ends in 005. Debug log from Desktop: https://gist.github.com/ec52423939aa52164ff55f4d3c40fe5a |
Do we know enough about this bug to remove the "iOS" and "Mac" bits from the title? |
I experience the same thing, as does someone else I talked with. Messages sent on Signal mobile from me appear duplicated when I use Signal desktop, though the recipient only sees them once. |
I spent some time investigating this today, and I have a couple questions and a couple requests. First a couple questions for those of you experiencing this:
Second, if you're willing, it would really help to know if these are truly different messages or a re-render problem. To determine if the application thinks about these as totally different messages, you can check these two places:
Thanks! |
I'm experiencing the same problem. In the past I can confirm that some messages duplicated, but it happened quite rarely and I don't remember exactly the context. Sometimes it happened for several messages in a row, but then it all went back to normal. For the second task I found it a little bit difficult to understand what you mean exactly. (I've downloaded the Signal Desktop app from here https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk). |
@lethargosapatheia Thanks for jumping in and trying to gather that additional information for us. If you're not familiar with using the Chrome Desktop Tools, then it will be a little more challenging for you. The idea is to see where the duplication occurs - if you're inspecting the right file (index.html) you'll be able to highlight different tags and you'll see them show up on the page. When you find the items that represent the duplicated messages, we want to know if the ids are the same. |
I see the same issue. I have disappearing messages enabled with someone who uses Signal Android (and desktop as well) while I have Signal iOS + Signal Desktop on macOS. Only my (the iOS/macOS) user's messages get duplicated on desktop. |
Also the spinning bar at the top is constantly there which might just be a disappearing messages feature but looks like a syncing thing and appears buggy to me, there are already indicators that disappearing messages are enabled. |
When I experience this, I only have my phone and desktop linked. I had zero duplicated messages, then I turned on expiring messages from my android device. All messages sent from android were shown twice on the desktop. After sending 3 messages, I shut off disappearing messages on the android device and no more duplicate messages appearing on the desktop from android. |
Signal Desktop 0.42.1, released to the Chrome Web Store today, has message de-duplication and a number of bug-fixes around disappearing messages. Please re-open this if you run into this behavior again. |
Bug description
Steps to reproduce
Actual result: Every message that was sent by myself on Signal iOS is received twice on Signal Desktop.
Expected result: Every message should be received only once on Desktop.
Screenshots
What I sent on Signal iOS:
Signal Desktop receiving everything twice:
Platform info
iOS: 10.3.1
Mac Browser: Google Chrome 58.0.3029.81
Desktop Signal version: 0.37.0
iOS Signal Version: 2.10.1
Link to debug log
Desktop: https://gist.github.com/4daf45818c79d54d27ba77dfce37f8e6
The text was updated successfully, but these errors were encountered: