Prepare upgrade to signal-cli 0.11.3 tpo solve current issues with Signal #289
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Due to some major issues with the older signal-cli due to API deprecation on server-side, I'm trying to built an up-to-date version of signal-cli-rest-api. (Issues: Unable to send/receive message due to DeprecatedExceptions, HTTP 499, etc. Upgrading signal-cli causes unreadable config file, etc.).
I already contributed to fixed the native build of the current
signal-cli. On integration it now seems that this requires libsignal 0.20.0.I tried to build that as well, but fail for the other platforms. Obviously
crossorcargoare picking the wrong linker, hence the linkage of the cross-plattform binaries fails. Not sure if this is running for you already, @bbernhard.So what IMHO remains to provide a hotfix release is to build the libsignal libs and updating the version.