{"action":"created","issue":{"url":"https://api.github.com/repos/signalapp/Signal-Desktop/issues/2762","repository_url":"https://api.github.com/repos/signalapp/Signal-Desktop","labels_url":"https://api.github.com/repos/signalapp/Signal-Desktop/issues/2762/labels{/name}","comments_url":"https://api.github.com/repos/signalapp/Signal-Desktop/issues/2762/comments","events_url":"https://api.github.com/repos/signalapp/Signal-Desktop/issues/2762/events","html_url":"https://github.com/signalapp/Signal-Desktop/issues/2762","id":365034472,"node_id":"MDU6SXNzdWUzNjUwMzQ0NzI=","number":2762,"title":"Error: No record for device +xx690.2 (shortly after PUT v1/messages/+xx690 409 Error) ","user":{"login":"five-c-d","id":42419492,"node_id":"MDQ6VXNlcjQyNDE5NDky","avatar_url":"https://avatars3.githubusercontent.com/u/42419492?v=4","gravatar_id":"","url":"https://api.github.com/users/five-c-d","html_url":"https://github.com/five-c-d","followers_url":"https://api.github.com/users/five-c-d/followers","following_url":"https://api.github.com/users/five-c-d/following{/other_user}","gists_url":"https://api.github.com/users/five-c-d/gists{/gist_id}","starred_url":"https://api.github.com/users/five-c-d/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/five-c-d/subscriptions","organizations_url":"https://api.github.com/users/five-c-d/orgs","repos_url":"https://api.github.com/users/five-c-d/repos","events_url":"https://api.github.com/users/five-c-d/events{/privacy}","received_events_url":"https://api.github.com/users/five-c-d/received_events","type":"User","site_admin":false},"labels":[{"id":738944613,"node_id":"MDU6TGFiZWw3Mzg5NDQ2MTM=","url":"https://api.github.com/repos/signalapp/Signal-Desktop/labels/Bug","name":"Bug","color":"f90c2c","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-09-28T20:45:57Z","updated_at":"2018-09-29T00:00:50Z","closed_at":null,"author_association":"NONE","body":"<!--\r\nPlease fill out this template with all the information you have. We can't do much without\r\nboth logs and a detailed description of what you encountered. Please do your best!\r\n\r\nPlease note that this tracker is only for bugs and feature requests. Please try these\r\nlocations if you have a question or comment:\r\n\r\n  https://community.signalusers.org/\r\n  http://support.signal.org/\r\n  support@signal.org\r\n\r\nLastly, be sure to preview your issue before saving. Thanks!\r\n-->\r\n\r\n* [x] I have searched open and closed issues for duplicates\r\n---\r\n\r\n### Bug description\r\n\r\nI successfully received a direct 2-way message from my contact xx690 yesterday -- they are using one phone plus <s>two</s><ins>correction: one</ins> linked device<s>s</s>.  I am using one phone plus one linked device, and both my devices received the message.  According to the debuglog from my linked device, this message was sent from xx690.1 <ins>which must be their signal4smartphone</ins>\r\n\r\nAround seven hours later, my contact sent a series of additional messages, one to me directly, and several to a groupchat we are both members of, which according to my logfiles were from xx690.2 this time around.  All these messages were received properly on my signal4android device, but none of them were received properly on my signal4desktop device.  First of all, the attemptd-messages were ALL shown in the 2-way conversation (rather than one in our 2-way conversation and the rest in the groupchat conversation).  Every message surfaced the same error -- \"Error handling incoming message\" and when viewing MoreInfo this was expanded to also say \"Error No record for device +1xx690.2\"  <ins>which must be their windows laptop</ins>\r\n\r\nAlthough it is not guaranteed to be the cause of the problem explained above, I am highly suspicious of this entry in the debuglog, which occurred prior to the happenings above: \r\n\r\n*  ERROR 2018-09-27T15:30:17.549Z PUT https://textsecure-service.whispersystems.org/v1/messages/+[REDACTED]690 409 Error \r\n*  INFO  2018-09-27T15:30:17.549Z deleting session for  +[REDACTED]690.2 \r\n\r\n### Steps to reproduce\r\n\r\n1.  install signal4android, install signal4linuxBeta, link the devices \r\n2.  have your contact install signal4smartphone, <s>install signal4desktop as xx690.1</s>, install another copy of signal4desktop as xx690.2, link them all \r\n3.  messages/attachments/calls without major incident for approx six weeks \r\n\r\nActual result:\r\n\r\nOut of the blue, you begin seeing the errors above.  In addition to several textual-content-only messages, a couple of the most recent attempted-messages the contact attempted to send a pdf ~375kb to groupchat, and a docfile ~36kb in the 2-way conversation, which HAS been done before (successfully).  \r\n\r\nExpected result:\r\n\r\nLack of the 'HTTP 409 Error' preferably, and especially lack of the 'Error No record for device', i.e. messaging continues successfully on all linked devices (not just signal4android) \r\n\r\n### Screenshots\r\n\r\n(Not needed... standard grey bubbles containing 'Error handling incoming message' italicized plus timestamp as well as with red-circle-around-red-exclamation-mark on the signal4desktop instance, and the corresponding standard grey bubbles with no red-icon and no errors on signal4android.) \r\n\r\n### Platform info\r\n\r\nSignal version:  v1.15.5-beta.1 \r\n\r\nOperating System:  Arch Linux 4.17 \r\n\r\nLinked device version: 4.25.10 when this error happened , but in the process of preparing the debuglogs it has auto-upgraded itself to 4.26.2 as of a short time ago \r\n\r\n### Link to debug log\r\n\r\nsignal4desktop == https://debuglogs.org/b63e560f345cb2312ac85c1f25ad5fe4b56830dc1e118c09573eca81d72fe59d\r\n\r\nsignal4android == https://debuglogs.org/e64060ee9bdf03ab9a4ad5c729433a383ccf815e0e2383eb783db8af8994c238\r\n\r\n### Searching turned up the following\r\n\r\n* Probably not related == https://github.com/signalapp/Signal-Desktop/issues/1088 , HTTP 409 thanks to local firewall-rules and (pre-electron) use of port 4433 , fixed by electron using standard https port 443 nowadays \r\n\r\n* Could be related == https://github.com/signalapp/Signal-Desktop/issues/1341 , No record for device + Error handling incoming message + messages okay on signal4android , closed as needing-new-debuglogs-from-signal4desktop-electron-not-chromeApp [might need to reopen? no 409 though] \r\n\r\n* Could be related == https://github.com/signalapp/Signal-Desktop/issues/1628 , \"Error handling incoming messages\" for all freshley imported msgs in electron App + HTTP **409** + Error Bad MAC \r\n\r\n* Probably not related == https://github.com/signalapp/Signal-Desktop/issues/1673 , HTTP 409 thanks to key problems caused by inadvertently copying another enduser's ~/.config/Signal into their own system by mistake , fixed by not doing that :-) \r\n\r\n* Vaguely related == https://github.com/signalapp/Signal-Desktop/issues/2052 , Changed contact name on iOS produces \"Error handling incoming message\" on Desktop + queueCached error handling item + Error: No record for device +[REDACTED]633.1 \r\n\r\n* Could be related == https://github.com/signalapp/Signal-Desktop/issues/2055 , \"Error handling incoming message\", \"No record for device\" on Windows client + sender of message recently upgraded their signal4windows to a later version [not sure if my contact received an auto-updated version of signal4desktop yesterday sometime?] \r\n\r\n* Probably not related == https://github.com/signalapp/Signal-Desktop/issues/2180 , HTTP 409 conflict which was always immediately followed by HTTP 413 rate-limiting , fixed by rebooting&resetting \r\n\r\n* Maybe related == https://github.com/signalapp/Signal-Desktop/issues/2286 , Invalid date + No record for device [phone number]**.2** ... [OP amichair's debuglog is no longer available (access denied), other people commenting in the thread had different issues] \r\n\r\n* Vaguely related == https://github.com/signalapp/Signal-Desktop/issues/2746 , \"Message encrypted for non-existing session\" after failed sync of a stale desktop client + No record for device + Failed to fetch prekey + Duplicate PreKeyMessage for session + Top-level unhandled promise rejection: MessageCounterError: Message key not found. The counter was repeated or the key was not filled. + queueDecryptedEnvelope error handling envelope HTTPError: promiseAjax: error response; code: 404\r\n\r\n### Other background info \r\n\r\nI have not closed my signal4desktop instance, nor otherwise interfered with it very much since noticing the error-messages (a couple of messages sent and received in other conversations).  Should I do anything else on this end?  Reboot?  Reset secure session on signal4android which is linked to the signal4desktop instance?  Reset secure session via the dev-console somehow?  Look for problems somewhere on the filesystem or in the databases perhaps on this end?  Upgrade to latest beta version of signal4desktop?  I do not have access to the sender's three devices and they will be VERY unlikely to want to mess around with trying to debug this problem with us.  That said, I'm happy to do what I can on this end, if there is anything which might help.  \r\n\r\nI noticed a bunch of HTTP 403 errors in my debuglogs related to three specific profiles... not sure what that is about, should I file a separate github issue?  \r\n\r\n* ERROR 2018-09-27T15:40:40.709Z GET https://cdn.signal.org/profiles/3f0_Cxs5WibhSiPJJ85DLQ 403 Error\r\n* ERROR 2018-09-27T15:40:45.005Z GET https://cdn.signal.org/profiles/7lcVzS-rO6Re5W5kDq-lUw 403 Error\r\n* ERROR 2018-09-27T15:46:59.725Z GET https://cdn.signal.org/profiles/iVQqlnFORZ0zQTbWfSwrgg 403 Error\r\n\r\n$ curl --insecure --url https://cdn.signal.org/profiles/iVQqlnFORZ0zQTbWfSwrgg\r\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\r\n<Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>34215EB5EFB4031F</RequestId><HostId>[REDACTED]</HostId></Error>\r\n\r\n$ curl --insecure --url https://cdn.signal.org/profiles/tZi6zHefLoFhwsUdtFX2dA\r\nWarning: Binary output [snip...]\r\n\r\n### Process bug\r\n\r\nOver in the righthand sidebar of this github-create-a-new-issue window, there is a little popup which says 'It looks like this is your first time opening an issue in this project! \\n Be sure to review the contributing guidelines.' with a link to here == https://github.com/signalapp/Signal-Desktop/blob/development/CONTRIBUTING.md  , but that is a helpdoc for people contributing pull-requests rather than for people filing new github-issues.  Unless... perhaps that was a not-so-subtle hint?  ;-)  "},"comment":{"url":"https://api.github.com/repos/signalapp/Signal-Desktop/issues/comments/425597324","html_url":"https://github.com/signalapp/Signal-Desktop/issues/2762#issuecomment-425597324","issue_url":"https://api.github.com/repos/signalapp/Signal-Desktop/issues/2762","id":425597324,"node_id":"MDEyOklzc3VlQ29tbWVudDQyNTU5NzMyNA==","user":{"login":"scottnonnenberg-signal","id":36971246,"node_id":"MDQ6VXNlcjM2OTcxMjQ2","avatar_url":"https://avatars1.githubusercontent.com/u/36971246?v=4","gravatar_id":"","url":"https://api.github.com/users/scottnonnenberg-signal","html_url":"https://github.com/scottnonnenberg-signal","followers_url":"https://api.github.com/users/scottnonnenberg-signal/followers","following_url":"https://api.github.com/users/scottnonnenberg-signal/following{/other_user}","gists_url":"https://api.github.com/users/scottnonnenberg-signal/gists{/gist_id}","starred_url":"https://api.github.com/users/scottnonnenberg-signal/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/scottnonnenberg-signal/subscriptions","organizations_url":"https://api.github.com/users/scottnonnenberg-signal/orgs","repos_url":"https://api.github.com/users/scottnonnenberg-signal/repos","events_url":"https://api.github.com/users/scottnonnenberg-signal/events{/privacy}","received_events_url":"https://api.github.com/users/scottnonnenberg-signal/received_events","type":"User","site_admin":false},"created_at":"2018-09-29T00:00:50Z","updated_at":"2018-09-29T00:00:50Z","author_association":"CONTRIBUTOR","body":"409 is generally about the server telling the requesting client that it has out-of-date information. You are required to send to every device that a given account owns when you send to them, and you have to have updated information for each to prove that you have a chance of communicating with them successfully. So the problem here is likely desktop's book-keeping before or after that call, but there is an outside chance that the server is responding with a 409 when it shouldn't."}}
{"actor":{"display_login":"scottnonnenberg-signal"}}