Chrome app stuck at "Syncing groups and contacts"

[lukehutch]

• [x] I have searched open and closed issues for duplicates

---

Bug description

I tried logging into Signal-Desktop using the QR code. The keys are successfully generated, but then the app gets stuck at "Syncing groups and contacts". I tried uninstalling and re-installing the Chrome app, but the same thing happened.

If I close the sync window then re-open Signal-Desktop without reinstalling it, it comes up fine, but without contacts or conversations synced.

Steps to reproduce

• Install Chrome app
• Generate QR code
• Hold up Signal Android app to register QR code

Actual result: Signal-Desktop connects, but gets stuck syncing Expected result: Signal-Desktop should sync

Screenshots

(Nothing special to see, just the sync window)

Platform info

Operating System: Fedora Linux 24 Browser: Chrome Signal version: 0.27.0

Link to debug log

https://gist.github.com/fc09e86f179a2fc3c40cf91dfb85bed8

[tigerhawkvok]

This duplicates on Windows 10 x64, on two different computers (custom desktop and Surface Pro 3).

Never gets past this screen:

The console log for the background inspector is:

(note the timestamps -- at that screenshot, it was stuck on syncing contacts for 11 minutes already)

If you close Signal then open it again, it will open, but there will be no contacts and no messages.

Chrome info:

Google Chrome   57.0.2986.0 (Official Build) dev (64-bit)
Revision    12c8d70173fc1a04fa588b75be71ab5e80655c60-refs/heads/master@{#444600}
OS  Windows 
JavaScript  V8 5.7.512
Flash   24.0.0.207 C:\Users\Philip\AppData\Local\Google\Chrome\User Data\PepperFlash\24.0.0.207\pepflashplayer.dll
User Agent  Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2986.0 Safari/537.36
Command Line    "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --enable-experimental-web-platform-features --enable-fast-unload --enable-features=AutomaticTabDiscarding,StaleWhileRevalidate2 --enable-google-branded-context-menu --enable-gpu-rasterization --enable-md-feedback --enable-md-policy-page --enable-offline-auto-reload --enable-offline-auto-reload-visible-only --enable-scroll-prediction --flag-switches-begin --flag-switches-end --google-profile-info --javascript-harmony --secondary-ui-md --show-saved-copy=primary --site-per-process --no-startup-window /prefetch:5 --flag-switches-begin --enable-experimental-web-platform-features --enable-fast-unload --enable-google-branded-context-menu --google-profile-info --enable-gpu-rasterization --javascript-harmony --enable-md-feedback --enable-md-policy-page --enable-offline-auto-reload-visible-only --enable-offline-auto-reload --enable-scroll-prediction --site-per-process --secondary-ui-md --show-saved-copy=primary --flag-switches-end

[michaelkirk]

Can you provide your mobile device log as well as specifying whether it’s Android or iOS?

On Jan 18, 2017, at 9:48 PM, Luke Hutchison notifications@github.com wrote:

I have searched open and closed issues for duplicates Bug description

I tried logging into Signal-Desktop using the QR code. The keys are successfully generated, but then the app gets stuck at "Syncing groups and contacts". I tried uninstalling and re-installing the Chrome app, but the same thing happened.

If I close the sync window then re-open Signal-Desktop without reinstalling it, it comes up fine, but without contacts or conversations synced.

Steps to reproduce

Install Chrome app Generate QR code Hold up Signal Android app to register QR code Actual result: Signal-Desktop connects, but gets stuck syncing Expected result: Signal-Desktop should sync

Screenshots

(Nothing special to see, just the sync window)

Platform info

Operating System: Fedora Linux 24 Browser: Chrome Signal version: 0.27.0

Link to debug log

https://gist.github.com/fc09e86f179a2fc3c40cf91dfb85bed8 https://gist.github.com/fc09e86f179a2fc3c40cf91dfb85bed8 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/WhisperSystems/Signal-Desktop/issues/1030, or mute the thread https://github.com/notifications/unsubscribe-auth/AANP4QHiTTHEse-MfBoqocYeLEWb-UF5ks5rTs8bgaJpZM4LnpUK.

[tigerhawkvok]

Here's my Android log: https://gist.github.com/06c237d425636e21aa03a4f4d1f9af3a

[liliakai]

Looks like the sync request, and other post-registration events, aren't getting triggered. We'll need to add some debug log output to figure out where we're getting stuck.

For now, you can probably workaround this by doing a manual contact import (from Settings) after you've restarted the app.

[dmleong]

Manual contact import no longer works for my desktop client (iOS mobile). They are both connected to the same wifi.

[michaelkirk]

@dmleong can you provide a log from your iOS device?

[liliakai]

And desktop log after attempting manual import?

[dmleong]

@michaelkirk here is the iOS log: https://gist.github.com/anonymous/1aa3dfd2f62dace86cd9f2e472ec5e12

@liliakai and the desktop log: https://gist.github.com/f09f9b0bc892d765b5a0da8d9a0accb0

Thanks ✨

[michaelkirk]

re: @dmleong

Hmmm. It looks like the iOS client is doing the right thing. I see a bunch of

[TSMessagesManager] Received requestContactssyncMessage.

all followed by a:

[TSMessagesManager] Successfully sent Contacts response syncMessage.

Most recently at 2017/01/23 10:33:13:527: https://gist.github.com/anonymous/1aa3dfd2f62dace86cd9f2e472ec5e12#file-org-whispersystems-signal-2017-01-22-23-49-log-L4104

See any issues on the Desktop end?

On Jan 23, 2017, at 3:44 PM, Danielle Leong notifications@github.com wrote:

@michaelkirk https://github.com/michaelkirk here is the iOS log: https://gist.github.com/anonymous/1aa3dfd2f62dace86cd9f2e472ec5e12 https://gist.github.com/anonymous/1aa3dfd2f62dace86cd9f2e472ec5e12 @liliakai https://github.com/liliakai and the desktop log: https://gist.github.com/f09f9b0bc892d765b5a0da8d9a0accb0 https://gist.github.com/f09f9b0bc892d765b5a0da8d9a0accb0 Thanks ✨

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/WhisperSystems/Signal-Desktop/issues/1030#issuecomment-274611052, or mute the thread https://github.com/notifications/unsubscribe-auth/AANP4feiUHnzyZ6IwgYxndL8u9gEvDC0ks5rVREegaJpZM4LnpUK.

[dmleong]

@michaelkirk the only thing I see that might be suspect is

2017-01-23T20:42:25.985Z New remote ephemeral key
2017-01-23T20:42:26.170Z Too many message keys for chain
2017-01-23T20:42:26.172Z MessageCounterError: Message key not found. The counter was repeated or the key was not filled.
2017-01-23T20:42:26.176Z MessageCounterError: Message key not found. The counter was repeated or the key was not filled.
    at chrome-extension://bikioccmkafdpakkkcpdbppfkghcmihk/js/libtextsecure.js:36386:25

Not familiar enough with the codebase to know if that's out of the ordinary or not

[liliakai]

In @dmleong's case we got the contact sync message back from iPhone but failed to decrypt it which means we have session corruption in the iPhone -> Desktop direction only. In particular, it looks like iPhone is encrypting using a session state that Desktop doesn't know about, and one with an unusually high value for its chain counter. Workaround is to do session reset with yourself. This doesn't explain the problem in the OP and should probably be a separate issue.

[dmleong]

@liliakai I'll be following up here: https://github.com/WhisperSystems/Signal-Desktop/issues/909

[lukehutch]

I went to grab my Android logs, so I opened up the Chrome app to initiate a sync, and weirdly it synced this time (without me changing anything). However, only two out of the three conversations in my Android app are showing up in the Chrome app, and the contact names are not all resolved in the Chrome app (one contact is showing up as a name on Android, but as a phone number in Chrome).

Logs are here: https://gist.github.com/anonymous/70eb8670c0e1cf27518da7e246f0c762

[michaelkirk]

On Jan 23, 2017, at 11:51 PM, Luke Hutchison notifications@github.com wrote:

I went to grab my Android logs, so I opened up the Chrome app to initiate a sync, and weirdly it synced this time (without me changing anything). However, only two out of the three conversations in my Android app are showing up in the Chrome app, and the contact names are not all resolved in the Chrome app (one contact is showing up as a name on Android, but as a phone number in Chrome).

Groups are synced from your phone separately from contacts. Does it look like all the groups synced but not the contacts?

What kind of network is your phone on?

Logs are here: https://gist.github.com/anonymous/70eb8670c0e1cf27518da7e246f0c762 https://gist.github.com/anonymous/70eb8670c0e1cf27518da7e246f0c762 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/WhisperSystems/Signal-Desktop/issues/1030#issuecomment-274709361, or mute the thread https://github.com/notifications/unsubscribe-auth/AANP4QeMOMCYJHEyJjFHj0xUQ3e8CVzGks5rVYNqgaJpZM4LnpUK.

[lukehutch]

Yes, one group I created synced fine,including the name. The one vibration that didn't show up was a test message I sent myself. The contact name that didn't show up on desktop was a single third party (not a group).

My phone is on wifi, behind two layers of NAT.

[tigerhawkvok]

More logs!

The desktop app:

The android logs:

https://gist.github.com/anonymous/53905ec7ef9a43b01da26887d0374d2f

[wolfgangrupprecht]

I'm seeing a sync failure too. Google Chrome on Linux (fedora) to Android phone (android **7.0). Both phone and computer were on the same networks for both IPv4 and IPv6.

https://gist.github.com/2a0d1c34c2f41a9041c49d2b46bbc704

[inferiorhumanorgans]

Ayup. Sync isn't working from iOS -> Chrome (OSX).

[michaelkirk]

@inferiorhumanorgans and anyone else having this problem - could you submit your Signal-Desktop debug log and your device log (e.g. on iOS go to settings > advanced > submit debug log) immediately after failing to sync?

You can induce a sync on desktop by going to Settings > "Import Now", under "Contacts"

Thanks!

[mgr100]

I'm seeing this as well on MacOS Sierra and on multiple versions of chrome.
I was able to import by forcing an import from settings. I wonder if this is a setup issue coming out of the installation.

[liliakai]

@mgr100 Please submit a debug log.

[mgr100]

https://gist.github.com/anonymous/294464720901861707ff17afab74bec9 Debug log Also the attached two two logs. I wondering if the import happened but the import screen never cleared.

Here are the two logs see comments in each. They would not upload so here they are on google drive

https://drive.google.com/open?id=0B1wnjf-4MHQcU0txX004YldhSUk https://drive.google.com/open?id=0B1wnjf-4MHQcM21PM1lERGpHSDg

[liliakai]

Seems like chrome's chrome.app.runtime.onMessage interface is failing to deliver registration events, or perhaps failing to bind event listeners. Not sure why. It seems to work reliably on my machine with a fresh install. The good news is I think we can/should switch to using Backbone.Events for this instead.

[mgr100]

I think that's a good call I've seen this on chrome canary which is bleeding edge also on the stable version.

On Tue, Feb 28, 2017 at 2:25 PM Lilia notifications@github.com wrote:

Seems like chrome's chrome.app.runtime.onMessage interface is failing to deliver registration events, or perhaps failing to bind event listeners. Not sure why. It seems to work reliably on my machine with a fresh install. The good news is I think we can/should switch to using Backbone.Events for this instead.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/WhisperSystems/Signal-Desktop/issues/1030#issuecomment-283137371, or mute the thread https://github.com/notifications/unsubscribe-auth/AE-1-CPRJPAJhXc7w1U6vcgmQh7XJw2aks5rhHS8gaJpZM4LnpUK .

[liliakai]

This was fixed in 886557a

[Arinerron]

@liliakai Huh. No matter how many times I reinstall the extension, browser, or even go to another operating system, it still doesn't work.

[scottnonnenberg]

@Arinerron Sorry you've been having such difficulty! If you go to chrome://extensions you can choose to inspect the 'background.html' file and see what we're logging, even if you haven't been able to fully set up the app. That would help us track down your problems.

[Arinerron]

@scottnonnenberg Np. Here's the full log. Now it seems to be getting stuck at "Generating keys" (I'm trying on another computer right now):

libtextsecure.js:22990 Invalid asm.js: Unexpected token
debugLog.js:49 pre-main prep time: 3 ms
debugLog.js:49 background page reloaded
debugLog.js:49 migration 1.0
debugLog.js:49 creating object stores
debugLog.js:49 migration 2.0
debugLog.js:49 migration 3.0
debugLog.js:49 migration 4.0
debugLog.js:49 migration 5.0
debugLog.js:49 migration 6.0
debugLog.js:49 migration 7.0
debugLog.js:49 creating debug log
debugLog.js:49 migration 8.0
debugLog.js:49 creating unread message index
debugLog.js:49 migration 9.0
debugLog.js:49 migration 10.0
debugLog.js:49 creating expiring message index
debugLog.js:49 migration 11.0
debugLog.js:49 creating expires_at message index
debugLog.js:49 migration 12.0
debugLog.js:49 cleaning up expiring messages with no expires_at
debugLog.js:49 migration 13.0
debugLog.js:49 Adding fields to identity keys
debugLog.js:49 migration 14.0
debugLog.js:49 Adding unprocessed message store
debugLog.js:49 migration 15.0
debugLog.js:49 Adding messages index for de-duplication
debugLog.js:49 new install
libsignal-protocol-worker.js:22851 Invalid asm.js: Unexpected token
libsignal-protocol-worker.js:22851 Invalid asm.js: Unexpected token
debugLog.js:49 ConversationController: starting initial fetch
debugLog.js:49 migrating search tokens
debugLog.js:49 migrating unread count
debugLog.js:49 migrating search tokens
2debugLog.js:49 migrating registration flags
debugLog.js:49 marking contacts and groups active
debugLog.js:49 listening for registration events
debugLog.js:49 ConversationController: done with initial fetch
debugLog.js:49 opening provisioning socket https://textsecure-service-ca.whispersystems.org:80
debugLog.js:49 provisioning socket open
debugLog.js:49 provisioning socket closed 1001
debugLog.js:49 PUT https://textsecure-service-ca.whispersystems.org:80/v1/devices/134749
libtextsecure.js:37645 OPTIONS https://textsecure-service-ca.whispersystems.org:80/v1/devices/134749 net::ERR_TUNNEL_CONNECTION_FAILED
(anonymous) @ libtextsecure.js:37645
promise_ajax @ libtextsecure.js:37598
retry_ajax @ libtextsecure.js:37656
ajax @ libtextsecure.js:37671
ajax @ libtextsecure.js:37717
confirmCode @ libtextsecure.js:37805
createAccount @ libtextsecure.js:38152
(anonymous) @ libtextsecure.js:38042
Promise resolved (async)
(anonymous) @ libtextsecure.js:38038
(anonymous) @ libtextsecure.js:40263
(anonymous) @ libtextsecure.js:40220
Async Call
queueTask @ libtextsecure.js:38110
(anonymous) @ libtextsecure.js:38037
Promise resolved (async)
handleRequest @ libtextsecure.js:38036
reader.onload @ libtextsecure.js:37211
FileReader (async)
socket.onmessage @ libtextsecure.js:37239
debugLog.js:49 PUT https://textsecure-service-ca.whispersystems.org:80/v1/devices/134749 0 Error
debugLog.js:49 PUT https://textsecure-service-ca.whispersystems.org:4433/v1/devices/134749
debugLog.js:49 PUT https://textsecure-service-ca.whispersystems.org:4433/v1/devices/134749 200 Success
debugLog.js:49 time travel detected!
debugLog.js:49 Active signed prekey: 1
debugLog.js:49 Old signed prekey record count: 0
debugLog.js:49 PUT https://textsecure-service-ca.whispersystems.org:80/v2/keys
libtextsecure.js:37645 OPTIONS https://textsecure-service-ca.whispersystems.org:80/v2/keys net::ERR_TUNNEL_CONNECTION_FAILED
(anonymous) @ libtextsecure.js:37645
promise_ajax @ libtextsecure.js:37598
retry_ajax @ libtextsecure.js:37656
ajax @ libtextsecure.js:37671
ajax @ libtextsecure.js:37717
registerKeys @ libtextsecure.js:37841
Promise resolved (async)
(anonymous) @ libtextsecure.js:38049
Promise resolved (async)
(anonymous) @ libtextsecure.js:38038
(anonymous) @ libtextsecure.js:40263
(anonymous) @ libtextsecure.js:40220
Async Call
queueTask @ libtextsecure.js:38110
(anonymous) @ libtextsecure.js:38037
Promise resolved (async)
handleRequest @ libtextsecure.js:38036
reader.onload @ libtextsecure.js:37211
FileReader (async)
socket.onmessage @ libtextsecure.js:37239
debugLog.js:49 PUT https://textsecure-service-ca.whispersystems.org:80/v2/keys 0 Error
debugLog.js:49 PUT https://textsecure-service-ca.whispersystems.org:4433/v2/keys
libtextsecure.js:37645 OPTIONS https://textsecure-service-ca.whispersystems.org:4433/v2/keys net::ERR_TUNNEL_CONNECTION_FAILED
(anonymous) @ libtextsecure.js:37645
promise_ajax @ libtextsecure.js:37598
retry_ajax @ libtextsecure.js:37656
(anonymous) @ libtextsecure.js:37660
setTimeout (async)
(anonymous) @ libtextsecure.js:37659
(anonymous) @ libtextsecure.js:37658
Promise rejected (async)
retry_ajax @ libtextsecure.js:37656
ajax @ libtextsecure.js:37671
ajax @ libtextsecure.js:37717
registerKeys @ libtextsecure.js:37841
Promise resolved (async)
(anonymous) @ libtextsecure.js:38049
Promise resolved (async)
(anonymous) @ libtextsecure.js:38038
(anonymous) @ libtextsecure.js:40263
(anonymous) @ libtextsecure.js:40220
Async Call
queueTask @ libtextsecure.js:38110
(anonymous) @ libtextsecure.js:38037
Promise resolved (async)
handleRequest @ libtextsecure.js:38036
reader.onload @ libtextsecure.js:37211
FileReader (async)
socket.onmessage @ libtextsecure.js:37239
debugLog.js:49 PUT https://textsecure-service-ca.whispersystems.org:4433/v2/keys 0 Error
debugLog.js:49 PUT https://textsecure-service-ca.whispersystems.org:8443/v2/keys
libtextsecure.js:37645 OPTIONS https://textsecure-service-ca.whispersystems.org:8443/v2/keys net::ERR_TUNNEL_CONNECTION_FAILED
(anonymous) @ libtextsecure.js:37645
promise_ajax @ libtextsecure.js:37598
retry_ajax @ libtextsecure.js:37656
(anonymous) @ libtextsecure.js:37660
setTimeout (async)
(anonymous) @ libtextsecure.js:37659
(anonymous) @ libtextsecure.js:37658
Promise rejected (async)
retry_ajax @ libtextsecure.js:37656
(anonymous) @ libtextsecure.js:37660
setTimeout (async)
(anonymous) @ libtextsecure.js:37659
(anonymous) @ libtextsecure.js:37658
Promise rejected (async)
retry_ajax @ libtextsecure.js:37656
ajax @ libtextsecure.js:37671
ajax @ libtextsecure.js:37717
registerKeys @ libtextsecure.js:37841
Promise resolved (async)
(anonymous) @ libtextsecure.js:38049
Promise resolved (async)
(anonymous) @ libtextsecure.js:38038
(anonymous) @ libtextsecure.js:40263
(anonymous) @ libtextsecure.js:40220
Async Call
queueTask @ libtextsecure.js:38110
(anonymous) @ libtextsecure.js:38037
Promise resolved (async)
handleRequest @ libtextsecure.js:38036
reader.onload @ libtextsecure.js:37211
FileReader (async)
socket.onmessage @ libtextsecure.js:37239
debugLog.js:49 PUT https://textsecure-service-ca.whispersystems.org:8443/v2/keys 0 Error
libtextsecure.js:37678 Uncaught (in promise) Error: Failed to connect to the server, please check your network connection.
    at ajax (libtextsecure.js:37670)
    at TextSecureServer.ajax (libtextsecure.js:37717)
    at TextSecureServer.registerKeys (libtextsecure.js:37841)
    at <anonymous>
HTTPError @ libtextsecure.js:37678
xhr.onerror @ libtextsecure.js:37643

The net::ERR_TUNNEL_CONNECTION_FAILED part made me think that maybe there's something wrong with my proxy settings. I already verified-- The traffic is not being routed through any proxies. I have pretty good internet speeds (and it's pretty reliable), so I doubt that's the problem.

Thanks a lot for your help!

[scottnonnenberg]

The ERR_TUNNEL_CONNECTION_FAILED entries in the log you posted do point to some sort of proxy problem. With a quick search I found people running into this kind of error on mobile networks. What kind of network are you connected to?

Lastly, it's probably time to promote this to an entirely new issue. We'd love to get the complete information from the template from you - what OS? What version of the app? Etc.