These are chat archives for gitterHQ/desktop

4th
Jun 2018
Piotr Esden-Tempski
@esden
Jun 04 00:00
but it is possible to launch it by starting /Applications/Gitter.app/Contents/MacOS/nwjs directly on the command line.
Eric Eastwood
@MadLittleMods
Jun 04 01:02

@esden http://update.gitter.im/osx/Gitter-4.1.0.dmg opens fine for me on macOS 10.12.6

The application is unsigned though and needs to be allowed in System preferences -> Security and Privacy -> Open anyway (after installed/dragged into applications folder)

Piotr Esden-Tempski
@esden
Jun 04 01:04
the problem is not the unsigned part. I am getting the following dialog on macOS 10.13.4 (17E202)
Screen Shot 2018-06-03 at 6.04.20 PM.png
I was able to install the 4.0.0 without problems, and just tell the system to ignore the missing signature.
The problem appeared when I overwrote the bundle with 4.1.0
Eric Eastwood
@MadLittleMods
Jun 04 01:06

@esden I don't have another machine to test with.

If you try to build it yourself, do you see the same issue?

Piotr Esden-Tempski
@esden
Jun 04 01:06
I will give it a try, and report as soon as I have tested it.
Piotr Esden-Tempski
@esden
Jun 04 01:33
humm I am having trouble with gulp:
% gulp build:osx                                                                                                                                                                                                                                             :(
gulp build:osx[30571]: ../src/node_contextify.cc:629:static void node::contextify::ContextifyScript::New(const FunctionCallbackInfo<v8::Value> &): Assertion `args[1]->IsString()' failed.
 1: node::Abort() [/usr/local/bin/node]
 2: node::MakeCallback(v8::Isolate*, v8::Local<v8::Object>, char const*, int, v8::Local<v8::Value>*, node::async_context) [/usr/local/bin/node]
 3: node::contextify::ContextifyScript::New(v8::FunctionCallbackInfo<v8::Value> const&) [/usr/local/bin/node]
 4: v8::internal::FunctionCallbackArguments::Call(v8::internal::CallHandlerInfo*) [/usr/local/bin/node]
 5: v8::internal::MaybeHandle<v8::internal::Object> v8::internal::(anonymous namespace)::HandleApiCallHelper<true>(v8::internal::Isolate*, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::FunctionTemplateInfo>, v8::internal::Handle<v8::internal::Object>, v8::internal::BuiltinArguments) [/usr/local/bin/node]
 6: v8::internal::Builtin_Impl_HandleApiCall(v8::internal::BuiltinArguments, v8::internal::Isolate*) [/usr/local/bin/node]
 7: 0x9c015d8427d
[1]    30571 abort (core dumped)  gulp build:osx
Piotr Esden-Tempski
@esden
Jun 04 01:42
for reference:
134 esdentem@batou ~/projects/gitter/desktop-git (git)-[master] % gulp -v                                                                                                                                                                                                                                                    :(
[18:40:17] CLI version 2.0.1
[18:40:17] Local version 3.9.1
esdentem@batou ~/projects/gitter/desktop-git (git)-[master] % node -v
v10.3.0
also, it starts up fine using npm start, so at least I can launch what I have cloned. The trouble is with the bundle creation. I have no knowledge about node.js or gulp, so I am only following the instructions as provided.
Eric Eastwood
@MadLittleMods
Jun 04 02:40
@esden Did you install the prereqs (you don't need the AWS stuff, only for distributing), https://gitlab.com/gitlab-org/gitter/desktop/#prerequisites
Piotr Esden-Tempski
@esden
Jun 04 04:03
Yes I did... :(
Eric Eastwood
@MadLittleMods
Jun 04 04:58

@esden Looks like it may be a problem with Node v10 and gulp 3.9.x, nodejs/node#20325

Here are my versions,

$ node -v
v6.14.2
$ gulp -v
[23:55:57] CLI version 3.9.0
[23:55:57] Local version 3.9.1
Ben Johnson
@cbj4074
Jun 04 13:25
@MadLittleMods Windows 7 and 10 :point_up: June 2, 2018 2:49 PM
Eric Eastwood
@MadLittleMods
Jun 04 17:20

@esden Just had two others try out http://update.gitter.im/osx/Gitter-4.1.0.dmg and it opened fine for them (one of them had macOS 10.13.4)

Any luck getting the build to work with a lesser version of Node.js?