Anyone else having issues with the getUserStatus
command?
#415
-
So this is weird, the function I implemented isn't working anymore. I ran it today and I'm getting the I just want to confirm if my setup is broken or if this function is throwing the exception for everyone. To be specific, I ran this command: Edit: I generated a stack trace: org.whispersystems.signalservice.api.push.exceptions.NonSuccessfulResponseCodeException: Unable to parse entity
at org.whispersystems.signalservice.internal.push.PushServiceSocket.retrieveDirectory(PushServiceSocket.java:776)
at org.whispersystems.signalservice.api.SignalServiceAccountManager.getContacts(SignalServiceAccountManager.java:384)
at org.asamk.signal.manager.Manager.areUsersRegistered(Manager.java:347)
at org.asamk.signal.commands.GetUserStatusCommand.handleCommand(GetUserStatusCommand.java:51)
at org.asamk.signal.Main.handleCommand(Main.java:214)
at org.asamk.signal.Main.init(Main.java:148)
at org.asamk.signal.Main.main(Main.java:69) |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
I see the same issue, looks like the signal server responds with 429 (Too Many Requests), maybe some rate limiting ... |
Beta Was this translation helpful? Give feedback.
-
Hello fellas (assumed). What would it take to have one (or both) of you implement getUserStatus so the result is available via dbus? Having signal-cli running in daemon mode, and need this functionality available in signal-cli and php-signal as soon as possible. I am willing to bounty the feature, if it's possible to do in the near future. I do PHP, but no Java. Please advise. Thanks. |
Beta Was this translation helpful? Give feedback.
I see the same issue, looks like the signal server responds with 429 (Too Many Requests), maybe some rate limiting ...
Would be interesting to check what Signal-Android uses to check which contacts are registered.