Error when sending and receiving in signal-cli any advice?

[andyengria]

Hi I have installed:
signal-cli 0.12.1 on a raspbery PI 4.
openjdk 17.0.7 2023-04-18
OpenJDK Runtime Environment (build 17.0.7+7-Raspbian-1deb11u1rpt1)
OpenJDK Client VM (build 17.0.7+7-Raspbian-1deb11u1rpt1, mixed mode, emulated-client)

• I have compiled libsignal
• updated the libsqlitejdbc.so in sqlite-jdbc-3.42.0.1.jar with rpi compiled version
• run trhough the signal-cli captcha install and verify steps successfully
• used updateProfile to set given-name and family-name
• run send which gives the following error
  java.lang.UnsatisfiedLinkError: 'boolean org.signal.libsignal.internal.Native.SessionRecord_HasSenderChain(long)'
  at org.signal.libsignal.internal.Native.SessionRecord_HasSenderChain(Native Method)
  at org.signal.libsignal.protocol.state.SessionRecord.hasSenderChain(SessionRecord.java:103)
  at org.asamk.signal.manager.storage.sessions.SessionStore.isActive(SessionStore.java:409)
  at org.asamk.signal.manager.storage.sessions.SessionStore.containsSession(SessionStore.java:155)
  at org.asamk.signal.manager.storage.protocol.SignalProtocolStore.containsSession(SignalProtocolStore.java:123)
  at org.whispersystems.signalservice.api.SignalServiceMessageSender.getEncryptedMessage(SignalServiceMessageSender.java:2581)
  at org.whispersystems.signalservice.api.SignalServiceMessageSender.getEncryptedMessages(SignalServiceMessageSender.java:2563)
  at org.whispersystems.signalservice.api.SignalServiceMessageSender.sendMessage(SignalServiceMessageSender.java:2169)
  at org.whispersystems.signalservice.api.SignalServiceMessageSender.sendContent(SignalServiceMessageSender.java:486)
  at org.whispersystems.signalservice.api.SignalServiceMessageSender.sendDataMessage(SignalServiceMessageSender.java:439)
  at org.asamk.signal.manager.helper.SendHelper.lambda$sendMessage$19(SendHelper.java:655)
  at org.asamk.signal.manager.helper.SendHelper.handleSendMessage(SendHelper.java:680)
  at org.asamk.signal.manager.helper.SendHelper.sendMessage(SendHelper.java:653)
  at org.asamk.signal.manager.helper.SendHelper.sendMessage(SendHelper.java:96)
  at org.asamk.signal.manager.internal.ManagerImpl.sendMessage(ManagerImpl.java:490)
  at org.asamk.signal.manager.internal.ManagerImpl.sendMessage(ManagerImpl.java:474)
  at org.asamk.signal.manager.internal.ManagerImpl.sendMessage(ManagerImpl.java:595)
  at org.asamk.signal.commands.SendCommand.handleCommand(SendCommand.java:227)
  at org.asamk.signal.commands.CommandHandler.handleLocalCommand(CommandHandler.java:35)
  at org.asamk.signal.App.handleLocalCommand(App.java:276)
  at org.asamk.signal.App.handleCommand(App.java:192)
  at org.asamk.signal.App.init(App.java:144)
  at org.asamk.signal.Main.main(Main.java:60)

and receive also errors (although the body text is received)
Envelope from: “Name” +441234567890 (device: 1) to +441234567890
Timestamp: 1697577657649 (2023-10-17T21:20:57.649Z)
Server timestamps: received: 1697577657630 (2023-10-17T21:20:57.630Z) delivered: 1697577681640 (2023-10-17T21:21:21.640Z)
Message timestamp: 1697577657649 (2023-10-17T21:20:57.649Z)
Body: Test again
With profile key

WARN ReceiveHelper - Message action failed.
java.lang.UnsatisfiedLinkError: 'boolean org.signal.libsignal.internal.Native.SessionRecord_HasSenderChain(long)'
at org.signal.libsignal.internal.Native.SessionRecord_HasSenderChain(Native Method)
at org.signal.libsignal.protocol.state.SessionRecord.hasSenderChain(SessionRecord.java:103)
at org.asamk.signal.manager.storage.sessions.SessionStore.isActive(SessionStore.java:409)
at org.asamk.signal.manager.storage.sessions.SessionStore.containsSession(SessionStore.java:155)
at org.asamk.signal.manager.storage.protocol.SignalProtocolStore.containsSession(SignalProtocolStore.java:123)
at org.whispersystems.signalservice.api.SignalServiceMessageSender.getEncryptedMessage(SignalServiceMessageSender.java:2581)
at org.whispersystems.signalservice.api.SignalServiceMessageSender.getEncryptedMessages(SignalServiceMessageSender.java:2563)
at org.whispersystems.signalservice.api.SignalServiceMessageSender.sendMessage(SignalServiceMessageSender.java:2169)
at org.whispersystems.signalservice.api.SignalServiceMessageSender.sendContent(SignalServiceMessageSender.java:486)
at org.whispersystems.signalservice.api.SignalServiceMessageSender.sendDataMessage(SignalServiceMessageSender.java:439)
at org.asamk.signal.manager.helper.SendHelper.lambda$sendProfileKey$1(SendHelper.java:144)
at org.asamk.signal.manager.helper.SendHelper.handleSendMessage(SendHelper.java:680)
at org.asamk.signal.manager.helper.SendHelper.sendProfileKey(SendHelper.java:143)
at org.asamk.signal.manager.actions.SendProfileKeyAction.execute(SendProfileKeyAction.java:18)
at org.asamk.signal.manager.helper.ReceiveHelper.handleQueuedActions(ReceiveHelper.java:302)
at org.asamk.signal.manager.helper.ReceiveHelper.receiveMessagesInternal(ReceiveHelper.java:173)
at org.asamk.signal.manager.helper.ReceiveHelper.receiveMessages(ReceiveHelper.java:107)
at org.asamk.signal.manager.internal.ManagerImpl.receiveMessages(ManagerImpl.java:1054)
at org.asamk.signal.manager.internal.ManagerImpl.receiveMessages(ManagerImpl.java:1040)
at org.asamk.signal.commands.ReceiveCommand.handleCommand(ReceiveCommand.java:81)
at org.asamk.signal.commands.CommandHandler.handleLocalCommand(CommandHandler.java:35)
at org.asamk.signal.App.handleLocalCommand(App.java:276)
at org.asamk.signal.App.handleCommand(App.java:192)
at org.asamk.signal.App.init(App.java:144)
at org.asamk.signal.Main.main(Main.java:60

Seems I got so far but not sure if there are any pointers anyone can give of where to start trying to fix this?
Thanks

[AsamK]

An UnsatisfiedLinkError indicates that something is seeing with the compiled libsignal-client library. Possibly the wedding version, https://github.com/AsamK/signal-cli/wiki/Provide-native-lib-for-libsignal#determine-the-required-libsignal-client-version

[andyengria]

Ah yes thanks that was it. I had the wrong libsignal-client version rather than the v0.30.0. required by signal-cli 0.12.1.
After downloading v 0.30.0 and recompiling and updating the jar per the guide the cli worked. thanks!