Tomasz
Tomasz
Hi, having the same issue here on the `/v1/receive` endpoint, additionally, the response for a `/v2/send` request fails with 400 and error message ```{"error":"strconv.ParseInt: parsing \"INFO SignalAccount - Config file...
> That sounds like a different error. Do you have multiple signal-cli-rest-api docker containers running? nope, definitely had only one instance running
It seems that this is not an issue with `signal-cli-rest-api`, but `signal-cli`... The culprit (at least for my issue, I can assume for OP's issue aswell) is that there are...
@bbernhard it seems the issue is actually here: ```go combinedOutput := stdoutBuffer.String() + stderrBuffer.String() ``` [snip](https://github.com/bbernhard/signal-cli-rest-api/blob/master/src/client/cli.go#L142) all logs are printed to stderr, and in this case we're returning the combined...
Right, so perhaps the actual fix would be for `signal-cli` to only log actual errors on stderr (if outputting json), skipping info and warn?
Yes, that would make sense, but it would also require to break the fix for #403 > I don't know the internals of signal-cli well enough, but what I would...
> Is the only problem that we don't escape a JSON injection? If so, couldn't we just do that? It should always be a good idea, not only for JSON...
> I would even make that not configureable and always return that information (or make it configureable and make the default `true`) For some endpoints including additional information would introduce...