Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

getProxyObject doesn't always return #36

Closed
sunnysidevibes opened this issue Sep 19, 2019 · 7 comments · Fixed by #48
Closed

getProxyObject doesn't always return #36

sunnysidevibes opened this issue Sep 19, 2019 · 7 comments · Fixed by #48

Comments

@sunnysidevibes
Copy link

I'm trying to use this library as a way to consume signal-cli's bus service. However, dbus-next won't ever return after calling
let obj = await bus.getProxyObject('org.asamk.Signal', '/org/asamk/Signal');

I also run into a similar issue when running the following lower level code:

  let methodCall = new Message({
    destination: 'org.asamk.Signal',
    path: '/org/asamk/Signal',
    interface: 'org.asamk.Signal',
    member: 'sendMessage',
    signature: 'sass',
    body: ['MessageText2', [], '17876776273']
  });

  let reply = await bus.call(methodCall);
  console.log(reply) #never runs
@acrisci
Copy link
Member

acrisci commented Sep 19, 2019

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

@sunnysidevibes
Copy link
Author

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

@djusHa
Copy link

djusHa commented Jan 26, 2020

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);

@acrisci
Copy link
Member

acrisci commented Jan 27, 2020

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.

@djusHa
Copy link

djusHa commented Jan 27, 2020

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/

@djusHa
Copy link

djusHa commented Jan 27, 2020

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

@acrisci
Copy link
Member

acrisci commented Feb 6, 2020

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

acrisci added a commit to acrisci/node-dbus-next that referenced this issue Feb 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants