-
Notifications
You must be signed in to change notification settings - Fork 57
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
Comments
Do you get the same if you use |
|
Hi, https://github.com/AsamK/signal-cli
|
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 |
you don't necesserily have to register signal on mobile phone, "normal" phone number does it too. Just: after that, there will be a call that tells you the verification number. Here you can unregister the number:https://signal.org/textsecure/unregister/ |
Have looked with dbus-monitor while running the script, nothing interesting... |
Ok I see the issue. The unmarshaller doesn't handle big endian messages. Everything else I've tested uses little endian. |
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:
The text was updated successfully, but these errors were encountered: