signal-cli receive error

[Tsjippy]

Running signal-cli receive on my RPI3 with version 0.13.11 gives me this error:

WARN SyncHelper - Sync contacts contained invalid contact, ignoring: Missing contact address! WARN JobExecutor - Job SyncStorageJob failed java.lang.AssertionError: Got unknown local storage record type: StorageId{type=6, raw=SyQEpJfAR30GYv1HRVPkqQ} at org.asamk.signal.manager.helper.StorageHelper.buildLocalStorageRecord(StorageHelper.java:560) at org.asamk.signal.manager.helper.StorageHelper.buildLocalStorageRecords(StorageHelper.java:522) at org.asamk.signal.manager.helper.StorageHelper.writeToStorage(StorageHelper.java:287) at org.asamk.signal.manager.helper.StorageHelper.syncDataWithStorage(StorageHelper.java:141) at org.asamk.signal.manager.jobs.SyncStorageJob.run(SyncStorageJob.java:30) at org.asamk.signal.manager.internal.JobExecutor.lambda$runNextJob$0(JobExecutor.java:59) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) at java.base/java.lang.Thread.run(Thread.java:1583) java.lang.OutOfMemoryError: Java heap space at org.whispersystems.signalservice.api.messages.multidevice.DeviceContactsInputStream.read(DeviceContactsInputStream.java:40) at org.asamk.signal.manager.helper.SyncHelper.handleSyncDeviceContacts(SyncHelper.java:366) at org.asamk.signal.manager.helper.IncomingMessageHandler$$Lambda/0x61f878a8.handle(Unknown Source) at org.asamk.signal.manager.helper.AttachmentHelper.retrieveAttachment(AttachmentHelper.java:119) at org.asamk.signal.manager.helper.IncomingMessageHandler.handleSyncMessage(IncomingMessageHandler.java:549) at org.asamk.signal.manager.helper.IncomingMessageHandler.handleMessage(IncomingMessageHandler.java:379) at org.asamk.signal.manager.helper.IncomingMessageHandler.checkAndHandleMessage(IncomingMessageHandler.java:271) at org.asamk.signal.manager.helper.IncomingMessageHandler.handleEnvelope(IncomingMessageHandler.java:189) at org.asamk.signal.manager.helper.ReceiveHelper.receiveMessagesInternal(ReceiveHelper.java:216) at org.asamk.signal.manager.helper.ReceiveHelper.receiveMessages(ReceiveHelper.java:107) at org.asamk.signal.manager.internal.ManagerImpl.receiveMessages(ManagerImpl.java:1326) at org.asamk.signal.manager.internal.ManagerImpl.receiveMessages(ManagerImpl.java:1295) at org.asamk.signal.commands.ReceiveCommand.handleCommand(ReceiveCommand.java:88) at org.asamk.signal.commands.CommandHandler.handleLocalCommand(CommandHandler.java:37) at org.asamk.signal.App.handleLocalCommand(App.java:278) at org.asamk.signal.App.handleCommand(App.java:179) at org.asamk.signal.App.init(App.java:144) at org.asamk.signal.Main.main(Main.java:56)

[Lukom]

I have the same warnings in logs, quite frequently:

WARN  JobExecutor - Job SyncStorageJob failed
java.lang.AssertionError: Got unknown local storage record type: StorageId{type=5, raw=ACNyauK6JN43Zse3anorXQ}
	at org.asamk.signal.manager.helper.StorageHelper.buildLocalStorageRecord(StorageHelper.java:562)
	at org.asamk.signal.manager.helper.StorageHelper.buildLocalStorageRecords(StorageHelper.java:523)
	at org.asamk.signal.manager.helper.StorageHelper.writeToStorage(StorageHelper.java:287)
	at org.asamk.signal.manager.helper.StorageHelper.syncDataWithStorage(StorageHelper.java:141)
	at org.asamk.signal.manager.jobs.SyncStorageJob.run(SyncStorageJob.java:30)
	at org.asamk.signal.manager.internal.JobExecutor.lambda$runNextJob$0(JobExecutor.java:59)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
	at java.base/java.lang.Thread.run(Thread.java:1583)

StorageId could be type=5 or type=6.

They started appearing after New Year, maybe earlier. I see them currently on `signal-0.13.12

[AsamK]

This is caused by storage records, that signal-cli doesn't support yet.
Can you check if it's fixed in the latest development build?
https://github.com/AsamK/signal-cli/actions/runs/13059277371

[m-ueberall]

AsamK/signal-cli/actions/runs/13059277371

@AsamK : Is it possible to restore the publication of the dependency-graph artefact? The local build script depends on it in order to recreate the necessary configuration locally. This must have broken earlier this week.

Unhandled error in Gradle post-action - job will continue: Error: Create Artifact Container failed: The artifact name dependency-graph is not valid. Request URL https://pipelinesghubeus21.actions.githubusercontent.com/BhHwoE6Q2rJKhhwc8Kv67PN4CrrgnrQBwRQNWFnqk2f538Tf0o/_apis/pipelines/workflows/13059615837/artifacts?api-version=6.0-preview

[Lukom]

I've tried that build from signal-cli-archive-21 on my Ubuntu Server 22.04, but it hangs:

JAVA_HOME=/usr/lib/jvm/java-21-openjdk-amd64 /home/k_deploy/signal-cli-0.13.13-SNAPSHOT/bin/signal-cli --trust-new-identities always --disable-send-log --output json daemon --http localhost:3300
INFO  DaemonCommand - Starting daemon in multi-account mode
INFO  HttpServerHandler - Started HTTP server on localhost/127.0.0.1:3300
WARN  RefreshRecipientsJob - Full CDSI recipients refresh failed, ignoring: org.signal.libsignal.net.CdsiProtocolException: Protocol error after establishing a connection (IOException)
...hangs...
^CINFO  Shutdown - Received SIGINT signal, shutting down ..