Hi Jana,
messages can not be received.
Behaviour is identical in the latest AppImage and the Linux-Version you helped me to build myself.
I had not gotten any messages so far, but was running openMittsu from a Terminal.
Then this happened: (slightly modified for public posting)
[2025-03-04 21:13:55.363] [main] [warning] Received an UNKNOWN packet with signature d2000000 and payload d2000000.
[2025-03-04 21:13:55.363] [main] [warning] Encountered an error while parsing payload of received message from 54xxxxxx with ID 45xxxxxxxxxxxxxx and time 20:59:20, on 04.03.2025: /home/oMPete/myBuildDir/openMittsu/src/messages/IncomingMessagesParser.cpp:28: Could not match message payload with signature byte 0xa0 to any existing MessageContents. Payload: a00a103c083d04066aebacfd276301fa1f427832a4010801102f1a97013d4c1747d8cfa9d6d9d4e3fa40c6fdff3da7894804f812aab3d26cca64fd55d37cff60460e0d8970d6e1a2f77251cb2483623b8415133902149b8523fcfb4138469efac107a8ec2819dd13fb06e4de3de15530ca6dcb8e3444207b91e2f2f440055e83f2dfabd6b5799563c8875595d56a42057b1a64fe537891028ef7fbf193e2fe3bb7c0f8d137e914deca14cde208202288202
The payload was: a00a103c083d04066aebacfd276301fa1f427832a4010801102f1a97013d4c1747d8cfa9d6d9d4e3fa40c6fdff3da7894804f812aab3d26cca64fd55d37cff60460e0d8970d6e1a2f77251cb2483623b8415133902149b8523fcfb4138469efac107a8ec2819dd13fb06e4de3de15530ca6dcb8e3444207b91e2f2f440055e83f2dfabd6b5799563c8875595d56a42057b1a64fe537891028ef7fbf193e2fe3bb7c0f8d137e914deca14cde208202288202
(Payload shortened by me for public posting)
The error repeats itself every time i connect to the network.
The ID of the Sender is ok, I know that Person, ID is in my Contacts.
Now, THIS is from the AppImage-Log: - Please note, that there is YOUR homefolder referenced. (I did not want to open another Issue for that)
[2025-03-04 21:11:40.520] [main] [warning] Received an UNKNOWN packet with signature d2000000 and payload d2000000.
[2025-03-04 21:11:40.546] [main] [warning] Encountered an error while parsing payload of received message from 54xxxxxx with ID 45xxxxxxxxxxxxxx and time 20:59:20, on 04.03.2025: /home/jana/Documents/openMittsu/src/messages/IncomingMessagesParser.cpp:28: Could not match message payload with signature byte 0xa0 to any existing MessageContents. Payload: a00a103c083d04066aebacfd276301fa1f427832a4010801102f1a97013d4c1747d8cfa9d6d9d4e3fa40c6fdff3da7894804f812aab3d26cca64fd55d37cff60460e0d8970d6e1a2f77251cb2483623b8415133902149b8523fcfb4138469efac107a8ec2819dd13fb06e4de3de15530ca6dcb8e3444207b91e2f2f440055e83f2dfabd6b5799563c8875595d56a42057b1a64fe537891028ef7fbf193e2fe3bb7c0f8d137e914deca14cde208202288202
The payload was: a00a103c083d04066aebacfd276301fa1f427832a4010801102f1a97013d4c1747d8cfa9d6d9d4e3fa40c6fdff3da7894804f812aab3d26cca64fd55d37cff60460e0d8970d6e1a2f77251cb2483623b8415133902149b8523fcfb4138469efac107a8ec2819dd13fb06e4de3de15530ca6dcb8e3444207b91e2f2f440055e83f2dfabd6b5799563c8875595d56a42057b1a64fe537891028ef7fbf193e2fe3bb7c0f8d137e914deca14cde208202288202
THIS time it looks to me, as if there really might be a problem in openMittsu.
regards oMPete
Hi Jana,
messages can not be received.
Behaviour is identical in the latest AppImage and the Linux-Version you helped me to build myself.
I had not gotten any messages so far, but was running openMittsu from a Terminal.
Then this happened: (slightly modified for public posting)
[2025-03-04 21:13:55.363] [main] [warning] Received an UNKNOWN packet with signature d2000000 and payload d2000000.
[2025-03-04 21:13:55.363] [main] [warning] Encountered an error while parsing payload of received message from 54xxxxxx with ID 45xxxxxxxxxxxxxx and time 20:59:20, on 04.03.2025: /home/oMPete/myBuildDir/openMittsu/src/messages/IncomingMessagesParser.cpp:28: Could not match message payload with signature byte 0xa0 to any existing MessageContents. Payload: a00a103c083d04066aebacfd276301fa1f427832a4010801102f1a97013d4c1747d8cfa9d6d9d4e3fa40c6fdff3da7894804f812aab3d26cca64fd55d37cff60460e0d8970d6e1a2f77251cb2483623b8415133902149b8523fcfb4138469efac107a8ec2819dd13fb06e4de3de15530ca6dcb8e3444207b91e2f2f440055e83f2dfabd6b5799563c8875595d56a42057b1a64fe537891028ef7fbf193e2fe3bb7c0f8d137e914deca14cde208202288202
The payload was: a00a103c083d04066aebacfd276301fa1f427832a4010801102f1a97013d4c1747d8cfa9d6d9d4e3fa40c6fdff3da7894804f812aab3d26cca64fd55d37cff60460e0d8970d6e1a2f77251cb2483623b8415133902149b8523fcfb4138469efac107a8ec2819dd13fb06e4de3de15530ca6dcb8e3444207b91e2f2f440055e83f2dfabd6b5799563c8875595d56a42057b1a64fe537891028ef7fbf193e2fe3bb7c0f8d137e914deca14cde208202288202
(Payload shortened by me for public posting)
The error repeats itself every time i connect to the network.
The ID of the Sender is ok, I know that Person, ID is in my Contacts.
Now, THIS is from the AppImage-Log: - Please note, that there is YOUR homefolder referenced. (I did not want to open another Issue for that)
[2025-03-04 21:11:40.520] [main] [warning] Received an UNKNOWN packet with signature d2000000 and payload d2000000.
[2025-03-04 21:11:40.546] [main] [warning] Encountered an error while parsing payload of received message from 54xxxxxx with ID 45xxxxxxxxxxxxxx and time 20:59:20, on 04.03.2025: /home/jana/Documents/openMittsu/src/messages/IncomingMessagesParser.cpp:28: Could not match message payload with signature byte 0xa0 to any existing MessageContents. Payload: a00a103c083d04066aebacfd276301fa1f427832a4010801102f1a97013d4c1747d8cfa9d6d9d4e3fa40c6fdff3da7894804f812aab3d26cca64fd55d37cff60460e0d8970d6e1a2f77251cb2483623b8415133902149b8523fcfb4138469efac107a8ec2819dd13fb06e4de3de15530ca6dcb8e3444207b91e2f2f440055e83f2dfabd6b5799563c8875595d56a42057b1a64fe537891028ef7fbf193e2fe3bb7c0f8d137e914deca14cde208202288202
The payload was: a00a103c083d04066aebacfd276301fa1f427832a4010801102f1a97013d4c1747d8cfa9d6d9d4e3fa40c6fdff3da7894804f812aab3d26cca64fd55d37cff60460e0d8970d6e1a2f77251cb2483623b8415133902149b8523fcfb4138469efac107a8ec2819dd13fb06e4de3de15530ca6dcb8e3444207b91e2f2f440055e83f2dfabd6b5799563c8875595d56a42057b1a64fe537891028ef7fbf193e2fe3bb7c0f8d137e914deca14cde208202288202
THIS time it looks to me, as if there really might be a problem in openMittsu.
regards oMPete