Signal-desktop: accessKey was provided, but senderCertificate was not

Created on 16 Jan 2020  路  46Comments  路  Source: signalapp/Signal-Desktop
  • [X] I have searched open and closed issues for duplicates

Bug Description

  1. Changed phone
  2. Linked my computer to Signal on my new phone
  3. Send message to 'x' contact
  4. The following error occurs:
"Error: OutgoingMessage.doSendMessage: accessKey was provided, but senderCertificate was not
    at OutgoingMessage.doSendMessage (file:///Applications/Signal.app/Contents/Resources/app.asar/js/libtextsecure.js:39956:9)
    at file:///Applications/Signal.app/Contents/Resources/app.asar/js/libtextsecure.js:39775:21
    at async OutgoingMessage.sendToNumber (file:///Applications/Signal.app/Contents/Resources/app.asar/js/libtextsecure.js:40183:7)"

...and the message cannot be send

Steps to Reproduce

  1. change phone
  2. install Signal on the phone
  3. register and setup Signal on the phone
  4. Link Signal on phone to Signal-Desktop on a computer
  5. Send a message to someone
  6. The error occurs

Actual Result:

Signal-desktop fails to send messages

Expected Result:

Signal-desktop should be able to send messages

Screenshots

Screenshot 2020-01-16 at 15 59 59

Platform Info

Signal-desktop Version: 1.29.4

Operating System:

MacOS Catalina 10.15.3 Beta

Linked Device Version:

Signal iOS version: 3.2.0.10

Link to Debug Log

Debug log

picture larssb
👍22 👀2 😄1 👎1

Most helpful comment

Please install v1.29.6 or v1.30.0-beta.6; both will fix this issue. Thanks for your patience today.

picture scottnonnenberg-signal on 17 Jan 2020
❤10

All 46 comments

Hmm reading through the debug log and the error is quite obvious: 

INFO  2020-01-16T15:14:23.293Z GET https://textsecure-service.whispersystems.org/v1/certificate/delivery
ERROR 2020-01-16T15:14:23.631Z GET https://textsecure-service.whispersystems.org/v1/certificate/delivery 503 Error

I'm using Pi-hole but have tried disabling that and then trying again. Then again. The response is HTTP503 which should be internal to the textsecure-service....

???

larssb picture larssb on 16 Jan 2020
😄1

worked for 1 message, then stopped working again. To another contact. Then stopped working again for that same contact

larssb picture larssb on 16 Jan 2020

I'm having the same issue here, just set up Signal Desktop on Mac with my Android phone, able to receive messages to desktop but cannot send.

From the failed message:
OutgoingMessage.doSendMessage: accessKey was provided, but senderCertificate was not

From the debug log:

```INFO 2020-01-16T14:44:35.075Z GET https://textsecure-service.whispersystems.org/v1/certificate/delivery
ERROR 2020-01-16T14:44:35.088Z GET https://textsecure-service.whispersystems.org/v1/certificate/delivery 503 Error
ERROR 2020-01-16T14:44:35.089Z refreshSenderCertificate: Get failed. Trying again in two minutes... HTTPError: promiseAjax: error response; code: 503
at HTTPError ([REDACTED]/app.asar/js/modules/web_api.js:379:13)
at [REDACTED]/app.asar/js/modules/web_api.js:335:13
at processTicksAndRejections (internal/process/task_queues.js:89:5)
Original stack:
Error
at _outerAjax ([REDACTED]/app.asar/js/modules/web_api.js:373:19)
at _ajax ([REDACTED]/app.asar/js/modules/web_api.js:476:14)
at Object.getSenderCertificate ([REDACTED]/app.asar/js/modules/web_api.js:531:14)
at run ([REDACTED]/app.asar/js/modules/refresh_sender_certificate.js:72:44)
at runWhenOnline ([REDACTED]/app.asar/js/modules/refresh_sender_certificate.js:95:7)

Output of a curl:

```$ curl -v https://textsecure-service.whispersystems.org/ -k
*   Trying 54.175.47.110...
* TCP_NODELAY set
* Connected to textsecure-service.whispersystems.org (54.175.47.110) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: C=US; ST=California; O=Open Whisper Systems; OU=Open Whisper Systems; CN=textsecure-service.whispersystems.org
*  start date: Feb 15 17:38:17 2019 GMT
*  expire date: Mar 12 18:20:20 2029 GMT
*  issuer: C=US; ST=California; L=San Francisco; O=Open Whisper Systems; OU=Open Whisper Systems; CN=TextSecure
*  SSL certificate verify result: self signed certificate in certificate chain (19), continuing anyway.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x7f9c0f00ec00)
> GET / HTTP/2
> Host: textsecure-service.whispersystems.org
> User-Agent: curl/7.54.0
> Accept: */*
> 
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
< HTTP/2 404 
< date: Thu, 16 Jan 2020 16:14:50 GMT
< content-type: application/json
< content-length: 43
< 
* Connection #0 to host textsecure-service.whispersystems.org left intact
{"code":404,"message":"HTTP 404 Not Found"}

Running Signal Desktop 1.29.4, MacOS Mojave 10.14.6, Signal Android 4.53.6
I tried rolling back to desktop versions 1.29.3 and 1.29.2 but the issue persisted. Verifying my safety number with a contact also did not resolve the issue. I have not been able to successfully send any messages.
Updating to Desktop 1.29.5 also has not helped.

jackfarzan picture jackfarzan on 16 Jan 2020
😄1 👍1

+1, having the same issue, with the same 503 error message:

ERROR 2020-01-16T16:02:35.270Z GET https://textsecure-service.whispersystems.org/v1/certificate/delivery 503 Error

503 wouldn't be PiHole related. Trying to hit the endpoint directly results in an untrusted cert.

bojanrajkovic picture bojanrajkovic on 16 Jan 2020
😄1 👍1

Yes, sorry:

Signal Desktop version: Linux, 1.29.4, running on Ubuntu 19.10
Linked device version: Signal for iOS, 3.1.1.1

bojanrajkovic picture bojanrajkovic on 16 Jan 2020
👍1

For what it's worth, I'm seeing the same error on Windows 10 (Signal v1.29.4) linked with Android (Signal v4.53.6).

AVee picture AVee on 16 Jan 2020
😄1

I'm having the same problem with Win10(signal 1.29.4) linked to android 10 running signal 4.53.6.

xlntech1 picture xlntech1 on 16 Jan 2020

Also having the same problem with Win10 (signal 1.29.4) linked to an Android 10 device running signal 4.53.6.

antonygl88 picture antonygl88 on 16 Jan 2020

I'm having the same problem.
Signal 1.29.4 on Ubuntu 19.04 linked to Android 10 device running Signal 4.53.6

thompsonplyler picture thompsonplyler on 16 Jan 2020

Also having the same problem with Win10 (signal 1.29.4) linked to a Pixel 3 XL running signal 4.53.7.

I can receive messages but I cant send. However, I can send to one contact who verified my safety number. Could that be an issue?

mickyaflalo picture mickyaflalo on 16 Jan 2020

Signal v1.29.5 released for Win10, just updated my machine and still getting the same errors.

I can receive messages however.

antonygl88 picture antonygl88 on 16 Jan 2020

Same issue here. v1.29.5 on macOS. Messages come in but cannot send.

mruszczyk picture mruszczyk on 16 Jan 2020 
INFO  2020-01-16T17:40:04.781Z SQL channel job 243 (updateConversations) succeeded in 16ms
INFO  2020-01-16T17:40:05.000Z SQL channel job 244 (getNextAttachmentDownloadJobs) succeeded in 11ms
ERROR 2020-01-16T17:40:05.419Z GET https://textsecure-service.whispersystems.org/v1/certificate/delivery 503 Error
ERROR 2020-01-16T17:40:05.420Z refreshSenderCertificate: Get failed. Trying again in two minutes... HTTPError: promiseAjax: error response; code: 503
    at HTTPError ([REDACTED]/app.asar/js/modules/web_api.js:379:13)
    at [REDACTED]/app.asar/js/modules/web_api.js:335:13
    at processTicksAndRejections (internal/process/task_queues.js:89:5)
Original stack:
Error
    at _outerAjax ([REDACTED]/app.asar/js/modules/web_api.js:373:19)
    at _ajax ([REDACTED]/app.asar/js/modules/web_api.js:476:14)
    at Object.getSenderCertificate ([REDACTED]/app.asar/js/modules/web_api.js:531:14)
    at run ([REDACTED]/app.asar/js/modules/refresh_sender_certificate.js:65:44)
    at runWhenOnline ([REDACTED]/app.asar/js/modules/refresh_sender_certificate.js:88:7)
INFO  2020-01-16T17:40:05.435Z GET https://textsecure-service.whispersystems.org/v1/profile/+[REDACTED]138 (unauth)
ERROR 2020-01-16T17:40:06.021Z GET https://textsecure-service.whispersystems.org/v1/profile/+[REDACTED]138 503 Error
ERROR 2020-01-16T17:40:06.022Z getProfile error: +[REDACTED]138 HTTPError: promiseAjax: error response; code: 503
    at HTTPError ([REDACTED]/app.asar/js/modules/web_api.js:379:13)
    at [REDACTED]/app.asar/js/modules/web_api.js:335:13
    at processTicksAndRejections (internal/process/task_queues.js:89:5)
Original stack:
Error
    at _outerAjax ([REDACTED]/app.asar/js/modules/web_api.js:373:19)
    at _ajax ([REDACTED]/app.asar/js/modules/web_api.js:476:14)
    at Object.getProfileUnauth ([REDACTED]/app.asar/js/modules/web_api.js:556:14)
    at MessageSender.getProfile (file://[REDACTED]/app.asar/js/libtextsecure.js:40746:26)
    at getProfile (file://[REDACTED]/app.asar/js/models/conversations.js:1660:50)
    at processTicksAndRejections (internal/process/task_queues.js:89:5)
    at async Promise.all (index 0)
INFO  2020-01-16T17:40:11.597Z Remove all notifications
INFO  2020-01-16T17:40:20.179Z Sending a keepalive message
INFO  2020-01-16T17:40:46.573Z Remove all notifications
INFO  2020-01-16T17:40:56.573Z Remove all notifications
INFO  2020-01-16T17:41:00.766Z Loaded this list of log files from logPath: log.log
simplymathematics picture simplymathematics on 16 Jan 2020

+1
Linux Mint 18.3
Signal v1.29.4
Linked to Signal iOS v3.2.0.10
Edit: Still an issue after upgrading to Signal v1.29.5.

zombitarian picture zombitarian on 16 Jan 2020

Same issue:
Win10
Signal v1.29.5
Linked to iOS

robholmesnz picture robholmesnz on 16 Jan 2020

Same Issue, Windows 10 and Android
Did it with v1.29.4 so upgraded to Signal v1.29.5 and same issue. Unsinstalled, reinstalled, and relinked and same issue.

OutgoingMessage.doSendMessage: accessKey was provided, but senderCertificate was not

drsaturday picture drsaturday on 16 Jan 2020

+1.
macOSMojave 10.14.6
Signal desktop app v1.29.5
Linked to Android (Signal 4.53.6)

Happy to provide logs if they are useful.

Sadgrinner picture Sadgrinner on 16 Jan 2020

+1
macOSMojave 10.14.6
Signal desktop app v1.29.5
Linked to iPhone (Signal 3.2.0.10)

bp360 picture bp360 on 16 Jan 2020

+1.
5.4.12-1-MANJARO
Signal desktop app v1.29.3
Linked to Android (Signal 4.53.6)

holive picture holive on 16 Jan 2020

+1
Kubuntu 19.10 - 5.3.0-26-generic kernel
Signal desktop v1.29.5
Linked to Android (v4.53.6)

linuxfingers picture linuxfingers on 16 Jan 2020

+1
ManjaroLinux 18.1.5
Signal desktop v1.29.4 (Flatpak)
Android Version : 4.53.6
Debug Log:
https://debuglogs.org/fabb70548c56ecf1fe9ae2afc3a7830c2d10c4c54de597d32f71a1660e1cac52

mdtita picture mdtita on 16 Jan 2020

+1
Signal desktop v1.29.4
linked to Signal 3.1.1.1 on iOS 12.4.4

Related: before the problem occured I got a notification that I had to re-link my signal on my pc, without any obvious cause. That never happened before. After relinking, the problem started. The problem does not occur in all conversations, but I havent had time to find the difference.

abxt45 picture abxt45 on 16 Jan 2020

+1
Signal Desktop Mac v1.29.5
linked to Signal 3.2.0.10 on iOS 13

Gui13 picture Gui13 on 16 Jan 2020

+1
Win10,
Signal Desktop v1.29.5
Signal Android newest

sik0vny picture sik0vny on 16 Jan 2020

+1
MacOs and app updated
iOS and app updated
Server issue?

TanguiC picture TanguiC on 16 Jan 2020

Window 10
Signal 1.29.5
Same issue.

zeromold picture zeromold on 16 Jan 2020

Same problem over here, both in Linux and Windows, using the latest (1.29.5) version.

In my case, this problem only occurred after re-linking Signal-Desktop. Using an already active instance (fully updated to 1.29.5) seems to work normally.

Debug log: https://debuglogs.org/186d34c08c8588dadd46030b69465f605d6741ed7c9cc4795447c9feb8321704

petcap picture petcap on 17 Jan 2020

+1
Windows 10 1903 and 1909
Signal Desktop v1.29.5
Signal Android 4.53.6

dshamblen17 picture dshamblen17 on 17 Jan 2020

https://textsecure-service.whispersystems.org certificate was issued 11 months ago, by TextSecure, which is not a trusted certificate authority. https://www.ssllabs.com/ssltest/analyze.html?d=textsecure%2dservice.whispersystems.org&s=54.175.130.206&hideResults=on&latest

Is this an Open Whisper Systems CA?

Edit: Perhaps this CA was trusted explicitly in the app and accidentally dropped in a recent update?

qskousen picture qskousen on 17 Jan 2020

Platform Info

  • Signal Version: v1.29.5 and v1.30.0-beta5
  • Operating System: Ubuntu 18.04 LTS
  • Linked Device Version: 4.53.7

Link to Debug Log

v1.29.5
https://debuglogs.org/f98548e7386caedc6c9d251b48f43f94409d699236afa3980886482abf1ca4c6
https://debuglogs.org/f480f0867f5b0b962705110b805345c91d9b35b1209b379e728333e639232a54

v1.30.0-beta5
https://debuglogs.org/366f06450f218863083cc4eabbbac884c9b0193eb6b51d6dee770d230df90923

guimspace picture guimspace on 17 Jan 2020

Also happening for me, same 503 error.

Samsung Note 5 on Android 7.0 with Signal 4.53.6

Windows 10 version 1809 with Signal 1.29.5

Link to debug log from Windows: https://debuglogs.org/2d44eab0313a2344f24df32fa2e0a30e9bfe09dbac548e3eaa3621a36717a408

PsiberPiRat picture PsiberPiRat on 17 Jan 2020

Wow, I thought it was just a problem with my new set-up. Could this be an issue with Signal itself? New machine, new installation of 1.29.5 Linux, can't send messages (but can receive):

OutgoingMessage.doSendMessage: accessKey was provided, but senderCertificate was not

I have previously used 1.29.3 and earlier on both Windows and Linux successfully.

ERROR 2020-01-17T06:12:37.982Z GET https://textsecure-service.whispersystems.org/v1/certificate/delivery 503 Error
ERROR 2020-01-17T06:12:37.983Z refreshSenderCertificate: Get failed. Trying again in two minutes... HTTPError: promiseAjax: error response; code: 503
    at HTTPError ([REDACTED]/app.asar/js/modules/web_api.js:379:13)
    at [REDACTED]/app.asar/js/modules/web_api.js:335:13
    at processTicksAndRejections (internal/process/task_queues.js:89:5)
Original stack:
Error
    at _outerAjax ([REDACTED]/app.asar/js/modules/web_api.js:373:19)
    at _ajax ([REDACTED]/app.asar/js/modules/web_api.js:476:14)
    at Object.getSenderCertificate ([REDACTED]/app.asar/js/modules/web_api.js:531:14)
    at run ([REDACTED]/app.asar/js/modules/refresh_sender_certificate.js:65:44)
    at runWhenOnline ([REDACTED]/app.asar/js/modules/refresh_sender_certificate.js:88:7)
    at Object.initialize ([REDACTED]/app.asar/js/modules/refresh_sender_certificate.js:30:3)
    at start (file://[REDACTED]/app.asar/js/background.js:1335:46)
INFO  2020-01-17T06:12:37.986Z GET https://textsecure-service.whispersystems.org/v1/profile/+[REDACTED]389 (unauth)
INFO  2020-01-17T06:12:37.990Z got request PUT /api/v1/queue/empty
INFO  2020-01-17T06:12:37.992Z MessageReceiver: finished processing messages after 'empty', now waiting for application
INFO  2020-01-17T06:12:37.992Z MessageReceiver: emitting 'empty' event
INFO  2020-01-17T06:12:37.993Z updater/start: Updates disabled - not starting new version checks
INFO  2020-01-17T06:12:37.993Z onEmpty: All outstanding database requests complete
ERROR 2020-01-17T06:12:39.309Z GET https://textsecure-service.whispersystems.org/v1/profile/+[REDACTED]389 503 Error
ERROR 2020-01-17T06:12:39.309Z getProfile error: +[REDACTED]389 HTTPError: promiseAjax: error response; code: 503
    at HTTPError ([REDACTED]/app.asar/js/modules/web_api.js:379:13)
    at [REDACTED]/app.asar/js/modules/web_api.js:335:13
    at processTicksAndRejections (internal/process/task_queues.js:89:5)
Original stack:
Error
    at _outerAjax ([REDACTED]/app.asar/js/modules/web_api.js:373:19)
    at _ajax ([REDACTED]/app.asar/js/modules/web_api.js:476:14)
    at Object.getProfileUnauth ([REDACTED]/app.asar/js/modules/web_api.js:556:14)
    at MessageSender.getProfile (file://[REDACTED]/app.asar/js/libtextsecure.js:40746:26)
    at getProfile (file://[REDACTED]/app.asar/js/models/conversations.js:1660:50)
    at processTicksAndRejections (internal/process/task_queues.js:89:5)
    at async Promise.all (index 0)
INFO  2020-01-17T06:12:39.750Z open inbox
INFO  2020-01-17T06:12:39.821Z GET https://textsecure-service.whispersystems.org/v1/profile/+[REDACTED]569 (unauth)
INFO  2020-01-17T06:12:39.824Z SQL channel job 33 (getMessageMetricsForConversation) succeeded in 50ms
INFO  2020-01-17T06:12:39.846Z SQL channel job 36 (saveMessage) succeeded in 15ms
ERROR 2020-01-17T06:12:40.071Z GET https://textsecure-service.whispersystems.org/v1/profile/+[REDACTED]569 503 Error
ERROR 2020-01-17T06:12:40.071Z getProfile error: +[REDACTED]569 HTTPError: promiseAjax: error response; code: 503
    at HTTPError ([REDACTED]/app.asar/js/modules/web_api.js:379:13)
    at [REDACTED]/app.asar/js/modules/web_api.js:335:13
    at processTicksAndRejections (internal/process/task_queues.js:89:5)
Original stack:
Error
    at _outerAjax ([REDACTED]/app.asar/js/modules/web_api.js:373:19)
    at _ajax ([REDACTED]/app.asar/js/modules/web_api.js:476:14)
    at Object.getProfileUnauth ([REDACTED]/app.asar/js/modules/web_api.js:556:14)
    at MessageSender.getProfile (file://[REDACTED]/app.asar/js/libtextsecure.js:40746:26)
    at getProfile (file://[REDACTED]/app.asar/js/models/conversations.js:1660:50)
    at async Promise.all (index 0)
INFO  2020-01-17T06:12:40.786Z SQL channel job 39 (updateConversations) succeeded in 19ms
ERROR 2020-01-17T06:12:42.553Z Top-level unhandled promise rejection: [object Object]
INFO  2020-01-17T06:12:43.807Z SQL channel job 42 (updateConversations) succeeded in 22ms
INFO  2020-01-17T06:12:43.892Z Send pre-checks took 2 milliseconds
INFO  2020-01-17T06:12:43.894Z Sending message to conversation +[REDACTED]569 with timestamp 1579241563894
ERROR 2020-01-17T06:12:43.922Z Top-level unhandled promise rejection: [object Object]
INFO  2020-01-17T06:12:43.938Z SQL channel job 43 (saveMessage) succeeded in 19ms
ERROR 2020-01-17T06:12:43.961Z Message.saveErrors: Failed to retrieve new device keys for number +[REDACTED]569 Error: OutgoingMessage.doSendMessage: accessKey was provided, but senderCertificate was not
    at OutgoingMessage.doSendMessage (file://[REDACTED]/app.asar/js/libtextsecure.js:39956:9)
    at file://[REDACTED]/app.asar/js/libtextsecure.js:39775:21
    at async OutgoingMessage.sendToNumber (file://[REDACTED]/app.asar/js/libtextsecure.js:40183:7)
INFO  2020-01-17T06:12:44.631Z SQL channel job 47 (updateConversations) succeeded in 13ms
INFO  2020-01-17T06:12:46.774Z Upgrade message schema (with index): {"done":true,"numProcessed":0,"fetchDuration":2,"upgradeDuration":0,"saveDuration":0,"totalDuration":2}
INFO  2020-01-17T06:12:46.774Z Background migration complete. Stopping idle detector.
INFO  2020-01-17T06:12:46.774Z Stop idle detector
ERROR 2020-01-17T06:12:46.926Z Top-level unhandled promise rejection: [object Object]

(Edited to show full section of debug log relevant to sending a message.)

Wedge009 picture Wedge009 on 17 Jan 2020

+1

same thing for me.

Error: OutgoingMessage.doSendMessage: accessKey was provided, but senderCertificate was not

deviantollam picture deviantollam on 17 Jan 2020

if anyone wants to check this Twitter thread... https://twitter.com/Agromahdi123/status/1218061188761903105 ...a few folk and i were unpacking what was up. it appears to be fixed now for me, upon an update to the Signal Desktop app minutes ago.

deviantollam picture deviantollam on 17 Jan 2020

fix confirmed in v1.29.6

I would be interested in an explanation and also why I had to suddenly had to re-link the desktop app?

abxt45 picture abxt45 on 17 Jan 2020

Signal will put out blog posts when things of note happen. maybe there will be some news. I'm just happy to see how quickly they got on this. I wish I hadn't opted to purge all of my previous messages when debugging it... but c'est la vie.

Always better to be sad about missing messages than to be sad about having KEPT message. That is often worse. =)

deviantollam picture deviantollam on 17 Jan 2020

Please install v1.29.6 or v1.30.0-beta.6; both will fix this issue. Thanks for your patience today.

scottnonnenberg-signal picture scottnonnenberg-signal on 17 Jan 2020
❤10

Just to provide additional context, some users encountered a bug related to refreshing the short-lived certificates that are used for Sealed Sender.

Messages could not be sent on Desktop. That's the full extent of the impact. If you were one of the affected users, we apologize for the inconvenience and appreciate your understanding.

jlund-signal picture jlund-signal on 17 Jan 2020
❤4

I've just tested the new versions and it is fixed. Thank you! But when I "reset secure session" in desktop, no message of "you reset the secure session" arrives in Android app - though it looks like it worked normally.

INFO  2020-01-17T08:32:00.866Z SQL channel job 580 (saveMessage) succeeded in 15ms
INFO  2020-01-17T08:32:00.866Z Upgrade message schema (with index): {"done":false,"numProcessed":1,"fetchDuration":4,"upgradeDuration":0,"saveDuration":15,"totalDuration":19}
INFO  2020-01-17T08:32:01.871Z next message expires 2020-01-18T08:30:54.486Z
INFO  2020-01-17T08:32:07.536Z resetting secure session
INFO  2020-01-17T08:32:07.537Z deleting sessions for +[REDACTED]333.1
INFO  2020-01-17T08:32:07.537Z deleting sessions for +[REDACTED]333.2
INFO  2020-01-17T08:32:07.537Z deleting sessions for +[REDACTED]333.3
INFO  2020-01-17T08:32:07.537Z finished closing local sessions, now sending to contact
INFO  2020-01-17T08:32:07.543Z GET https://textsecure-service.whispersystems.org/v2/keys/+[REDACTED]333/1 (unauth)
INFO  2020-01-17T08:32:07.548Z PUT https://textsecure-service.whispersystems.org/v1/messages/+[REDACTED]649
INFO  2020-01-17T08:32:07.772Z PUT https://textsecure-service.whispersystems.org/v1/messages/+[REDACTED]649 200 Success
INFO  2020-01-17T08:32:07.773Z GET https://textsecure-service.whispersystems.org/v2/keys/+[REDACTED]333/1 200 Success
INFO  2020-01-17T08:32:07.777Z GET https://textsecure-service.whispersystems.org/v2/keys/+[REDACTED]333/2 (unauth)
INFO  2020-01-17T08:32:07.982Z GET https://textsecure-service.whispersystems.org/v2/keys/+[REDACTED]333/2 200 Success
INFO  2020-01-17T08:32:08.001Z GET https://textsecure-service.whispersystems.org/v2/keys/+[REDACTED]333/3 (unauth)
INFO  2020-01-17T08:32:08.287Z GET https://textsecure-service.whispersystems.org/v2/keys/+[REDACTED]333/3 200 Success
INFO  2020-01-17T08:32:08.321Z PUT https://textsecure-service.whispersystems.org/v1/messages/+[REDACTED]333 (unauth)
INFO  2020-01-17T08:32:08.517Z next message expires 2020-01-18T08:30:54.486Z
INFO  2020-01-17T08:32:08.561Z SQL channel job 589 (updateConversations) succeeded in 15ms
INFO  2020-01-17T08:32:08.593Z PUT https://textsecure-service.whispersystems.org/v1/messages/+[REDACTED]333 200 Success
INFO  2020-01-17T08:32:08.593Z deleting sessions for +[REDACTED]333.1
INFO  2020-01-17T08:32:08.593Z deleting sessions for +[REDACTED]333.2
INFO  2020-01-17T08:32:08.593Z deleting sessions for +[REDACTED]333.3
INFO  2020-01-17T08:32:08.616Z SQL channel job 590 (saveMessage) succeeded in 17ms
INFO  2020-01-17T08:32:09.116Z SQL channel job 592 (createOrUpdateSessions) succeeded in 21ms
INFO  2020-01-17T08:32:10.972Z Loaded this list of log files from logPath: log.log
guimspace picture guimspace on 17 Jan 2020

Thank you for the quick response. I haven't confirmed resolution yet but given what others have said,it seems to be. Good that the issue was specific to desktop version too - I suspect there won't be many affected since most people seem to prefer mobile phones.

Wedge009 picture Wedge009 on 17 Jan 2020

Can confirm, the latest update fixed it for me.

dellitsni picture dellitsni on 17 Jan 2020

I can also confirm that it works now with v1.29.6 ... @jlund-signal thank you for the background to the issue. Couldn't this be closed now?

larssb picture larssb on 17 Jan 2020

Update: v1.29.6 seems to have fixed the issue (at least for me)

zombitarian picture zombitarian on 17 Jan 2020

Working today with update v1.29.6 on Win10

antonygl88 picture antonygl88 on 17 Jan 2020

Issue re-emerged with update to v1.29.6 on Windows 10 as of 2 minutes from
this point.

linuxfingers picture linuxfingers on 17 Jan 2020

I'm going to close this, since the issue does appear to be resolved.

@guimspace @linuxfingers Please enter new bugs, following the standard bug template. Thanks!

scottnonnenberg-signal picture scottnonnenberg-signal on 17 Jan 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

halb9 picture halb9  路  3Comments
hanzei picture hanzei  路  3Comments
jeremymasters picture jeremymasters  路  3Comments
github-cygwin picture github-cygwin  路  3Comments
lokesh-krishna picture lokesh-krishna  路  3Comments