throneless-tech / libsignal-service-javascript

A javascript library for basic interaction with the Signal messaging service, adapted from Signal-Desktop.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Not working

Tsjippy opened this issue · comments

Hi thanks for this great project.

This is the first time I dive into the world of NPM so maybe I ask stupidquestions.

How exactly do I start this project?

I wanted to run the example so I did this on my windows computer:
cd D:\test
npm install --save @throneless/libsignal-service
npm install node-localstorage

it all installed fine. I added an STORE environmental variable with the value D:\test\store

Then I run node ./examples/client.js requestSMS +234******* 1234567890
I received an sms just fine, but it gave me a warning:

(node:19920) V8: D:\test\node_modules@throneless\libsignal-protocol\build\curve25519_concat.js:20225 Invalid asm.js: Expected shift of word size

I then registered:
node ./examples/client.js register +234******** 1234567890 ******

It gave me this response:

(node:9176) V8: D:\test\node_modules@throneless\libsignal-protocol\build\curve25519_concat.js:20225 Invalid asm.js: Expected shift of word size
(Use node --trace-warnings ... to show where the warning was created)
undefined

I then sended a message to another number:
node ./examples/client.js send +234************** Test

It gave me this response:

(node:21344) V8: D:\test\node_modules@throneless\libsignal-protocol\build\curve25519_concat.js:20225 Invalid asm.js: Expected shift of word size
(Use node --trace-warnings ... to show where the warning was created)
V1 session storage migration error: registrationId undefined for open session version undefined
V1 session storage migration error: registrationId undefined for open session version undefined
{
successfulIdentifiers: [ '+2349********' ],
failoverIdentifiers: [],
errors: [],
unidentifiedDeliveries: [],
dataMessage: <Buffer 0a 04 74 65 73 74 32 08 e2 f0 f6 a3 2e 65 c4 e5 38 b2 d7 83 c2 f4 2e>
}

but that person never received the message

turned out I had to add an NODE_ENV variable iwth value production