Bernhard B.
Bernhard B.
With the next release the number should now be returned in normal and native mode. But in json-rpc mode the output comes directly from [signal-cli](https://github.com/AsamK/signal-cli). I guess I could manually...
> Very interesting information, so if nextcloud doesn't get it right in the next few days then I'll probably have to switch too. > > I also find it unacceptable...
Have you tried using the `json-rpc` mode? Do you observe the same behavior there? Since you are already playing around with the underlying `signal-cli`: Here is the full documentation: https://github.com/AsamK/signal-cli/blob/master/man/signal-cli.1.adoc...
Please use a double quote (`"`) instead of a single quote (`'`) when specifying the group.
> Going into `json-rpc` mode in the container I was unable to call the CLI - it kept saying it was already running Sorry, should have been more clear. Connecting...
Thanks for the report! > I think the fix would be to, in signal-cli-rest-api, parse the returned string into an object, return it with c.JSON(200, obj), and add the object...
unfortunately this is an upstream issue: https://github.com/AsamK/signal-cli/issues/1556
Please give this version a try: `bbernhard/signal-cli-rest-api:0.164-dev`
Please give this version a try: `bbernhard/signal-cli-rest-api:0.167-dev`
With the next release it is is possible to escape formatting characters by prefixing them with two backslashes. If you want to give it a try, let me know. Then...