Signal app does not get rendered #5528

onny · 2016-12-07T19:27:08Z

Hey,
I'm using ArchLinux x64 with the latest version of nwjs (0.19) and signal (0.27).
Signal is a Chrome app for secure messaging and it worked fine with nwjs in previous version.

In the registration process window, everything is fine:

After that, the message and contact list window doesn't get rendered:

Is there a way to debug this? Can I switch to another rendering engine for testing purposes?

Best regards,
Jonas

rogerwang · 2016-12-07T22:16:02Z

Does it happen with 0.18.8?

…

On Thu, Dec 8, 2016, 3:27 AM Jonas Heinrich ***@***.***> wrote: Hey, I'm using ArchLinux x64 with the latest version of nwjs (0.19) and signal (0.27). Signal <https://github.com/WhisperSystems/Signal-Desktop> is a Chrome app for secure messaging and it worked fine with nwjs in previous version. In the registration process window, everything is fine: [image: 2016-12-07-201924_swaygrab] <https://cloud.githubusercontent.com/assets/757752/20983020/30bac792-bcbb-11e6-87ad-30b34f466fd5.png> After that, the message and contact list window doesn't get rendered: [image: 2016-12-07-202504_swaygrab] <https://cloud.githubusercontent.com/assets/757752/20983040/409b5744-bcbb-11e6-8a1a-34526e62617c.png> Is there a way to debug this? Can I switch to another rendering engine for testing purposes? Best regards, Jonas — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#5528>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAKGGW6F5CrIox8fyZ8vUUCDLqTtdBD4ks5rFwiPgaJpZM4LG_-f> .

onny · 2016-12-08T12:38:50Z

The bug was introduced in version 0.17.4 and since then not fixed.
With version 0.17.3:

Version 0.17.4:

So maybe I have to further git bisect the issue?!

rogerwang · 2016-12-09T01:20:54Z

@onny No need to bisect, thanks. We'll try to fix it here.

xzhan96 · 2016-12-21T06:53:23Z

@onny Does the app can be launched in Ubuntu? I got the error "Failed to load extension from: ... Signal-Desktop.Localization used, but default_locale wasn't specified in the manifest" when launching it.

onny · 2016-12-21T11:46:18Z

This should work:

wget https://github.com/WhisperSystems/Signal-Desktop/archive/v0.27.0.tar.gz
tar xvf v0.27.0.tar.gz
cd Signal-Desktop-0.27.0
npm install
node_modules/grunt-cli/bin/grunt
nw ../Signal-Desktop-0.27.0

In ArchLinux I need following packages as make dependency:

npm 4.0.5
ruby-sass 3.4.22

xzhan96 · 2016-12-27T01:50:26Z

@onny I always got error as below:

$ npm install
npm WARN signal-desktop@0.0.0 No license field.
$ node_modules/grunt-cli/bin/grunt
...
Running "copy:src" (copy) task
Warning: Error while processing "js/expire.js" file. Use --force to continue.
Aborted due to warnings.

My sass version is Sass 3.4.23 and ruby is ruby 2.4.0p0 (2016-12-24 revision 57164) [x86_64-linux]

onny · 2016-12-27T09:55:03Z

Thanks @xzhan96 for helping out!
For me this is just a warning which I can ignore. Here's a setup instruction for Ubuntu x86_64 16.10:

sudo aptitude install npm ruby-sass nodejs-legacy
cd /tmp
wget "https://github.com/WhisperSystems/Signal-Desktop/archive/v0.27.0.tar.gz"
tar xvf v0.27.0.tar.gz
cd Signal-Desktop-0.27.0
npm install
node_modules/grunt-cli/bin/grunt
cd /tmp 
wget "https://dl.nwjs.io/v0.19.3/nwjs-v0.19.3-linux-x64.tar.gz"
tar xvf nwjs-v0.19.3-linux-x64.tar.gz
nwjs-v0.19.3-linux-x64/nw Signal-Desktop-0.27.0

Unfortunately I get another error message there, I wans't able to fix yet:

Failed to load extension from: /tmp/Signal-Desktop-0.27.0. Localization used, but default_locale wasn't specified in the manifest.

xzhan96 · 2016-12-28T08:35:29Z

@onny you also can't launch the Signal application in Ubuntu?

onny · 2016-12-28T11:18:41Z

Nope in Ubuntu I cannot start it yet :( This might be related to the npm and ruby versions Ubuntu is using.

onny · 2016-12-28T11:45:17Z

Oh sorry I was wrong. Now it is working! This instruction is working for Ubuntu x86_64 16.10:

sudo aptitude install npm ruby-sass nodejs-legacy
cd /tmp
wget "https://github.com/WhisperSystems/Signal-Desktop/archive/v0.27.0.tar.gz"
tar xvf v0.27.0.tar.gz
cd Signal-Desktop-0.27.0
npm install
node_modules/grunt-cli/bin/grunt
cd /tmp 
wget "https://dl.nwjs.io/v0.19.3/nwjs-v0.19.3-linux-x64.tar.gz"
tar xvf nwjs-v0.19.3-linux-x64.tar.gz
nwjs-v0.19.3-linux-x64/nw Signal-Desktop-0.27.0/dist

You have to run the dist folder with nwjs, not the Signal source folder!

Now this issue is also reproducable with Ubuntu. Here's the screenshot:

The error Aborted due to warnings. in grunt can be ignored and is probably not related.

xzhan96 · 2016-12-29T02:52:15Z

@onny is this means the Signal works well?

You can see I am using the same nwjs version with you.

onny · 2016-12-29T08:22:32Z

No unfortunately you have to sign in into Signal. It is the main chat window which doesn't get rendered, see #5528 (comment)

xzhan96 · 2017-01-03T01:48:36Z

Sorry, I was on holiday leave in the past three days.
But I can't connect the server...

onny · 2017-01-03T08:31:46Z

Ups, maybe you live in a country where it is censored? Then you might be relay on using a VPN connection?

xzhan96 · 2017-01-04T01:28:07Z

yes, but I already have proxy and can access google, youtube, wiki, etc.

rogerwang · 2017-01-04T01:41:52Z

@xzhan96 are you able to access the same URL used by the app (use --v=1 to see the URL in log). Some sites here are blocked by DNS poisoning (e.g. twitter) so it might be different with google, youtube and wikipedia.

xzhan96 · 2017-01-04T05:31:58Z

@rogerwang is this right? I can't get any log..
./nwjs-v0.19.3-linux-x64/nw --v=1 Signal-Desktop-0.27.0/dist/

rogerwang · 2017-01-04T05:51:58Z

@xzhan96 http://docs.nwjs.io/en/latest/For%20Users/FAQ/#consolelog-doesnt-output-to-linux-terminal

xzhan96 · 2017-01-04T05:59:36Z

got the error message:

[15044:15044:0104/140246:INFO:CONSOLE(37881)] "WebSocket connection to 'wss://textsecure-service-ca.whispersystems.org:80/v1/websocket/provisioning/?agent=OWD' failed: WebSocket opening handshake timed out", source: chrome-extension://hcbcgommcbcbahdndhccilpnghopdoic/js/libtextsecure.js (37881)
[15044:15044:0104/140246:INFO:CONSOLE(49)] "websocket closed", source: chrome-extension://hcbcgommcbcbahdndhccilpnghopdoic/js/debugLog.js (49)
[15044:15044:0104/140256:INFO:CONSOLE(49)] "opening provisioning socket", source: chrome-extension://hcbcgommcbcbahdndhccilpnghopdoic/js/debugLog.js (49)

rogerwang · 2017-01-04T06:24:46Z

It looks more likely a network issue on your side @xzhan96 . Please see it to reproduce OP's issue.

xzhan96 · 2017-01-04T07:02:04Z

thanks a lot @rogerwang, I can reproduce now

xzhan96 · 2017-01-10T04:59:25Z

error message:

[26069:26069:0109/135645:VERBOSE1:dispatcher.cc(442)] Num tracked contexts: 2
[26036:26036:0109/135645:INFO:CONSOLE(753)] "Uncaught TypeError: Cannot read property 'Window' of undefined", source: extensions::nw.Window (753)
[26036:26036:0109/135645:INFO:CONSOLE(49)] "open inbox", source: chrome-extension://hcbcgommcbcbahdndhccilpnghopdoic/js/debugLog.js (49)
[26036:26036:0109/135645:INFO:CONSOLE(49)] "TypeError: Cannot read property 'Window' of undefined", source: chrome-extension://hcbcgommcbcbahdndhccilpnghopdoic/js/debugLog.js (49)
[26036:26036:0109/135645:INFO:CONSOLE(206)] "Uncaught TypeError: Cannot read property 'Window' of undefined", source: extensions::app.window (206)

xzhan96 · 2017-01-10T06:21:36Z

it's related with #5294

onny · 2017-01-10T21:17:29Z

But this bug doesn't seem to be fixed yet?

xzhan96 · 2017-01-11T01:33:12Z

yes, knows the reason, working on how to fix..

onny · 2017-02-02T12:56:56Z

Bug still present in signal 0.28 and nwjs 0.20!

GnorTech · 2017-02-02T14:51:23Z

@onny will see to fix it in 0.20.2. Thanks for your patience. (we just tagged the 0.20.1 release for chromium 56.0.2924.87 update).

GnorTech · 2017-02-06T01:09:36Z

@xzhan96 since this bug is impacting users and need to be fixed soon. I'll follow up with your work. Thanks.

GnorTech · 2017-02-06T04:42:56Z

@onny the issue is fixed in git and can be downloaded via http://dl.nwjs.io/live-build/02-06-2017/nw20-3567769-e9d818b-a2ef613-1f1f729/v0.20.2/

Sorry for the delay due to the holiday here.

onny · 2017-03-29T11:56:00Z

Unfortunately this issue still appears on other platforms. One person reported to me that this bug still occours on KDE Linux desktop and I was able to reproduce it on Windows 7 (x64). Here's how to setup nwjs and Signal on Windows:

Download and extract Signal Desktop: https://github.com/WhisperSystems/Signal-Desktop/archive/v0.33.0.zip
Download and install nwjs for Windows: https://dl.nwjs.io/v0.21.3/nwjs-v0.21.3-win-x64.zip
Download and install nodejs: https://nodejs.org/dist/v6.10.1/node-v6.10.1-x64.msi
Download and install Ruby: https://dl.bintray.com/oneclick/rubyinstaller/rubyinstaller-2.3.3-x64.exe
Open CMD, run following commands:

cd Signal-Desktop-0.33.0
npm install
npm install -g grunt-cli
gem install sass
grunt -f
cd ../nwjs-v0.21.3-win-x64
nw.exe ../Signal-Desktop-0.33.0/dist

If grunt somehow fails to compile the app on Windows, here's also a precompiled package I've uploaded:
https://nextcloud.project-insanity.org/index.php/s/2HEUJ4MyxUpN9di

After starting Signal app with nwjs, it looks like this:

rogerwang · 2017-03-29T12:22:02Z

@Christywl please verify this first.

Christywl · 2017-03-30T08:11:22Z

npm install fails on my Windows, so I try the precompiled package https://nextcloud.project-insanity.org/index.php/s/2HEUJ4MyxUpN9di, Signal app with a white screen opens and some errors are in the devtools console:

Windows 10/nwjs-sdk-v0.21.3

onny · 2017-04-08T10:48:43Z

Bug is still present in:

node 7.8.0 https://nodejs.org/dist/v7.8.0/node-v7.8.0-x64.msi
nwjs 0.21.5 https://dl.nwjs.io/v0.21.5/nwjs-v0.21.5-win-x64.zip
signal-desktop 0.35.0 https://github.com/WhisperSystems/Signal-Desktop/archive/v0.35.0.tar.gz
ruby 2.3.3 https://dl.bintray.com/oneclick/rubyinstaller/rubyinstaller-2.3.3-x64.exe

I managed to "compile" the signal app on windows. I guess the problem here was that WinRAR couldn't extract the signal archive completely because it contained symlinks. I had to run WinRAR as administrator to extract everything.

Even though there's still an error at the end, signal app should run fine with nwjs :(

Christywl · 2017-11-24T06:45:11Z

@onny, does this issue still reproduce in your device? I still can't make it work on my device. Some errors occur when running 'grunt -f'.

Running "concat:components" (concat) task
File js/components.js created.

Running "concat:libtextsecurecomponents" (concat) task
File libtextsecure/components.js created.

Running "concat:test" (concat) task
File test/test.js created.

Running "concat:libtextsecure" (concat) task
File js/libtextsecure.js created.

Running "concat:libtextsecuretest" (concat) task
File libtextsecure/test/test.js created.

Running "sass:stylesheets" (sass) task
Error: Invalid CSS after "...ntlTelInput.css": expected "{", was ""
        on line 1 of stylesheets/_intlTelInput.scss
        from line 2 of stylesheets/options.scss
  Use --trace for backtrace.
Warning: Exited with error code 13 Used --force, continuing.
Error: Invalid CSS after ".../demo/emoji.css": expected "{", was ""
        on line 1 of stylesheets/_emoji.scss
        from line 13 of stylesheets/manifest.scss
  Use --trace for backtrace.
Warning: Exited with error code 13 Used --force, continuing.

Use your precompiled package, it displays a white screen as my previous comment said.

onny · 2017-11-24T20:26:17Z

Sorry @Christywl, I'm not using the app anymore, can't test it :(

ghostoy added the needinfo label Dec 8, 2016

rogerwang removed the needinfo label Dec 9, 2016

rogerwang assigned sunlin-link Dec 9, 2016

sunlin-link added core-team triaged labels Dec 20, 2016

xzhan96 assigned xzhan96 and unassigned sunlin-link Dec 21, 2016

xzhan96 removed the triaged label Dec 21, 2016

GnorTech assigned GnorTech and unassigned xzhan96 Feb 6, 2017

GnorTech closed this as completed Feb 6, 2017

onny mentioned this issue Feb 14, 2017

Signal app always restarts setup wizard even it's already configured #5704

Closed

rogerwang reopened this Mar 29, 2017

rogerwang assigned rogerwang and unassigned GnorTech Mar 29, 2017

sunlin-link removed the core-team label Jul 3, 2017

Christywl added the needinfo label Nov 24, 2017

rogerwang closed this as completed Nov 25, 2017

Signal app does not get rendered #5528

Signal app does not get rendered #5528

Comments

onny commented Dec 7, 2016

rogerwang commented Dec 7, 2016 via email

onny commented Dec 8, 2016 • edited Loading

rogerwang commented Dec 9, 2016

xzhan96 commented Dec 21, 2016

onny commented Dec 21, 2016 • edited Loading

xzhan96 commented Dec 27, 2016

onny commented Dec 27, 2016 • edited Loading

xzhan96 commented Dec 28, 2016

onny commented Dec 28, 2016

onny commented Dec 28, 2016 • edited Loading

xzhan96 commented Dec 29, 2016 • edited Loading

onny commented Dec 29, 2016

xzhan96 commented Jan 3, 2017 • edited Loading

onny commented Jan 3, 2017

xzhan96 commented Jan 4, 2017

rogerwang commented Jan 4, 2017

xzhan96 commented Jan 4, 2017

rogerwang commented Jan 4, 2017

xzhan96 commented Jan 4, 2017

rogerwang commented Jan 4, 2017

xzhan96 commented Jan 4, 2017

xzhan96 commented Jan 10, 2017 • edited Loading

xzhan96 commented Jan 10, 2017

onny commented Jan 10, 2017

xzhan96 commented Jan 11, 2017

onny commented Feb 2, 2017 • edited Loading

GnorTech commented Feb 2, 2017

GnorTech commented Feb 6, 2017

GnorTech commented Feb 6, 2017

onny commented Mar 29, 2017

rogerwang commented Mar 29, 2017

Christywl commented Mar 30, 2017

onny commented Apr 8, 2017 • edited Loading

Christywl commented Nov 24, 2017

onny commented Nov 24, 2017

onny commented Dec 8, 2016 •

edited

Loading

onny commented Dec 21, 2016 •

edited

Loading

onny commented Dec 27, 2016 •

edited

Loading

onny commented Dec 28, 2016 •

edited

Loading

xzhan96 commented Dec 29, 2016 •

edited

Loading

xzhan96 commented Jan 3, 2017 •

edited

Loading

xzhan96 commented Jan 10, 2017 •

edited

Loading

onny commented Feb 2, 2017 •

edited

Loading

onny commented Apr 8, 2017 •

edited

Loading