Skip to content

Conversation

redbullpeter
Copy link

This brings the required whatsmeow library version up to most recent commit dated 27th May 2025.

The API has changed and expects the context to be passed as the first parameter.

Otherwise there are no other changes.

This has been tested on a live system and in the last 24 hours there appears to be no issues.

@pazkero
Copy link

pazkero commented Jun 8, 2025

I can confirm it works with 2025-05-27 Whatsmeow. Do note it won't work with 2025-05-30 version.

@antonizoon
Copy link

I can merge this pull request into my fork as part of making a release to cover outstanding matterbridge problems, but I'd need to get confirmation that its fixed with whatsmeow 05-30 or if we should go with 05-27 long term.

I'm going to start maintaining a fork of matterbridge to accept and merge pull requests regarding irc -> matrix -> discord since our organization needs this bridge to work. if @42wim ever returns I can then make a big pull request back, or just keep accepting pull requests indefinitely.

However, I can only test irc -> matrix -> discord so will need more people to help provide pull requests proven to fix the whatsapp and telegram issues. If anyone else is able to help test whatsapp and telegram please provide tested pull requests.

https://github.com/bibanon/matterbridge/

Download linux intel 64-bit binary: https://github.com/bibanon/matterbridge/releases/tag/v1.26.1

If anyone knows how to generate the go builds for non-linux platforms, let me know. I'll only generate releases for linux intel 64-bit until then.

@pazkero
Copy link

pazkero commented Jun 22, 2025

@antonizoon @redbullpeter No, this PR did not work with May 30th version, only with May 27th version, as I previously stated.

Trying to use with May 30th version gives an error, and eventually a segmentation fault when iirc trying to relay a message. It doesn't even tries to sync avatars/profiles pics.

Regards,

@selfhoster1312
Copy link

@pazkero Do you have an uptream whatsmeow ticket tracking what doesn't work with later releases and why? Otherwise do you have time to test if it's been fixed?

@AndreySV
Copy link

Update to 20250527 doesn't work anymore with following error:

[Client ERROR] Client outdated (405) connect failure (client version: 2.3000.1022781640)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants