io.github.brevilo.jolm.Utils$OlmException: BAD_MESSAGE_FORMAT about jolm HOT 7 CLOSED

Hi @oncecrossover and welcome to the "team"! Glad you like it so far 👍

I'll try and have a look at it over the weekend. In the meantime, which version of libolm are you using?

from jolm.

In the meantime, a few quick hints:

• The plainText in Session.encrypt() doesn't refer to the actual message content you want to send, but to an event payload codified in JSON.
• The session you're using is an Olm session. For its plaintext payload content and format please see this.
• I think en-/decrypting a m.room_key event might do as a test.
• For a general introduction of all things E2E I recommend the official guide. It's certainly not the most well-written (or structured) guide but I'm not aware of a better resource.
• See that guide's section on Olm encryption for more details on the Session.encrypt() payload.

Hope this helps

from jolm.

Also, would you be fine with me adding your (modified) test as unit test, or do you rather want to submit a PR if and when you got your's working (for proper attribution)?

Thanks

from jolm.

Hello,

We are using 3.2.6 version.

BTW, We have encrypted message on Java, and decrypted on Android, it working fine.

from jolm.

Also, would you be fine with me adding your (modified) test as unit test, or do you rather want to submit a PR if and when you got your's working (for proper attribution)?

Thanks

Sure, I'm happy to contribute code. what's more important now is that we need a full unit test as soon as possible, our development work is broken here. could you quickly provide a unit test based on my test code? @brevilo

from jolm.

Hi @oncecrossover, you indeed hit a bug 😇

I fixed it in #3 (or the fix-2 branch). Could you please test it and report back before I merge it?
(Ignore the build failure in the PR checks, that's an unrelated GitHub workflow issue)

Thanks!

from jolm.

Hey @brevilo , it works on the fix-2 branch. 👍

from jolm.