getProxyObject doesn't always return about node-dbus-next HOT 7 CLOSED

Do you get the same if you use dbus-send?

from node-dbus-next.

dbus-send does work.

dbus-send --session --type=method_call --print-reply --dest="org.asamk.Signal" /org/asamk/Signal org.asamk.Signal.sendMessage string:[MESSAGE] array:string: string:[RECIPIENT]
method return sender=:1.38 -> dest=:1.43 reply_serial=2

from node-dbus-next.

Hi,
i can confirm this. No return if using getProxyObject() on signal-cli.
No matter if system bus or session bus.

https://github.com/AsamK/signal-cli

const SIGNAL_BUSNAME = 'org.asamk.Signal';
const SIGNAL_OBJECTPATH = '/org/asamk/Signal';

let obj = await bus.getProxyObject(SIGNAL_BUSNAME, SIGNAL_OBJECTPATH);

from node-dbus-next.

It's hard for me to set up because I don't have signal right now and I have to go through the whole process to test it.

Try to run that while running dbus-monitor and see if there's anything interesting.

from node-dbus-next.

you don't necesserily have to register signal on mobile phone, "normal" phone number does it too.

Just:
signal-cli -u <phonenumber in int. format> register --voice

after that, there will be a call that tells you the verification number.

Here you can unregister the number:https://signal.org/textsecure/unregister/

from node-dbus-next.

Have looked with dbus-monitor while running the script, nothing interesting...

from node-dbus-next.

Ok I see the issue. The unmarshaller doesn't handle big endian messages. Everything else I've tested uses little endian.

from node-dbus-next.