-
-
Notifications
You must be signed in to change notification settings - Fork 301
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
0.12.7 - signal-cli version is too old for the Signal-Server, please update. #1439
Comments
i got the same problem since the same time |
Also getting this with v0.12.7 |
Yeah, I had only just yesterday upgraded to 0.12.7 (with Java 21 on Debian 12) due to this message occurring with an older version of signal-cli, and now this message returned with the latest released version. Any updates will be muchly appreciated. adTHANKSvance TL;DR:
I'm using the straight up java version in /opt/signal... that runs against Java 21. No containers or anything so running directly within Debian 12.
|
Looks like the dependencies have been updated 4 days ago. But there is no build yet: |
Is there a way to know ahead of time when Signal swervers will begin blocking certain client versions so that the client(s) can be updated ahead of time? |
Hello. Does anyone know when the update will be released? |
Same problem here any news on an update? |
I created a fork that built the latest version. And it works with my preliminary tests. So on your own risk and with no further guarateed support you can use the following binaries https://github.com/key-lime-box/signal-cli/releases/tag/v0.12.7_patch2 or the following image: ghcr.io/key-lime-box/signal-cli:0.12.7_patch2 |
Sorry just fixed the path. |
thank you for the patch. Is there a way to update signal-cli without completely reinstalling it? Beacause i down't want to go through with the complete linking procedure again. |
In theory you should be able to just replace the jar file and restart it. Although i'm not familiar with your set-up. I also recommend backing up you settings and account data before doing this. |
Thank you very much. I am not using signal-cil for the primary device, so I did not backup my data. I replaced the file and it works fine for me |
Thank, for me signal-cli-0.12.8-SNAPSHOT worked, jdk-21-oracle-x64 and native lib 0.39.2 https://github.com/signalapp/libsignal/releases/ |
With the 0.12.7_patch2 version I get
This is with debian bookworm/12, with the default jre/jdk (openjdk-17-jre-headless). |
Hi, I am getting this error: what are the steps to install? Do i just overwrite the signal-cli executable in /usr/bin then drop the lib folder in the /usr/bin ? |
Same here |
This is to be expected as upstream snapshots produced by the |
In my environment (debian bullseye/11), I had to manually download the openjdk-21 build (from here: https://jdk.java.net/21/), untar that into /usr/local and put the 'bin' directory into my PATH (PATH="/usr/local/jdk-21.0.2/bin:$PATH"), and then I was able to run the patched version. $ signal-cli --version |
I think it is stated in another issue that Java 21 is required by 0.12.7. |
THX, this worked for me with openjdk-21 on debian 12.4 |
Thanks! In my environment (details above) I was able to unpack When 0.12.8 is officially released, I'll do a similar couple of steps. |
Great - but would it eventually also be possible to do a second build like signal-cli_ubuntu2004_amd64.gz without the "aggressive CPU optimisations"-problem (see #1363)? :-) Tnx! |
I see 0.12.7_patch2 as a [functional] stopgap until there is time for 0.12.8 to be fully vetted and released officially. Just my humble observation. |
I just released version 0.12.8, which just updates the user agent. |
Thanks so much for the quick response. When you server stops signaling you, you get twitchy. ;-) |
Note, upon using the patch, then using official 0.12.8, this error occurs:
Apparently the internal versioning doesn't quite agree, with the patch posted earlier representing itself as a "newer" version than the official release. So if you went from 0.12.7 to 0.12.8 I imagine you'd be OK, but if you used 0.12.8_patch2 after 0.12.7 then tried to go to 0.12.8, you will have problems. At least I did. I thus had to go back to the 0.12.7_patch2 version and will continue using it until some future time. |
I cannot use 0.12.8 without re-registering, it seems. any workaround for this? I think maybe this issue should stay open for a bit. |
Is there any fix for debian bullseye available? Due to #1363 the official version does no longer work. |
@msedv did you find any solution for older hosts? |
@m-ueberall any chance to get a new version here? https://media.projektzentrisch.de/temp/signal-cli/ |
@disaster123: Yes, these are currently being tested. With a bit of luck, they should be publicly available within an hour. |
@m-ueberall thanks a lot! Works fine! |
I've switch to the debian docker image: |
Okay, listen, I know I'm going to sound a bit crazy here. If I go to this page in Firefox and click the link for If I hit "copy link" and say Spooky, probably not relevant, but figured I'd say something. |
The file name is provided with the URL (https://objects.githubusercontent.com/..filename%3D**signal-cli-0.12.8-Linux-native.tar.gz**), but the server sends also as response header
The browser takes the latter, while wget takes the former, apparently. If you download using
you also get the 0.12.7 name ¯_(ツ)_/¯ |
Oops, premature celebration, I'm still getting the wrong file. |
I´m unable to send messages using signal-cli 0.12.7 since about half an hour.
The server tells me the following:
Error while checking account +XXXXX: signal-cli version is too old for the Signal-Server, please update.
I´m using the "bbernhard/signal-cli-rest-api" Docker-Container with 0.12.7 embedded.
The text was updated successfully, but these errors were encountered: