Zender - WhatsApp and SMS Messaging Platform and use Android as SMS Gateways (SaaS) v3.10.2

Zender - WhatsApp and SMS Messaging Platform and use Android as SMS Gateways (SaaS) Changelog

Changelog v3.10.2

• Updated the WhatsApp server. Replace your titansys-whatsapp binary with the one in this release's WhatsApp folder, or the two WhatsApp fixes below will not take effect.
• Changed the WhatsApp server so it no longer marks incoming messages as read by default. Linking an account used to mark every incoming message as read immediately, which silently stopped notifications from appearing on that phone. If you do want messages marked as read automatically, start the server with --autoread.
• Fixed the system updater reporting a successful update when it had actually copied nothing. It now checks that every file it needs to replace can be written before it starts, stops if a file fails to copy instead of carrying on, and records the new version only once everything else is in place.
• Fixed a failed database step during an update being ignored. The update now stops and reports the problem rather than continuing on and deleting files.
• Improved the message shown when a WhatsApp QR code cannot be generated. Instead of one generic error you are now told the actual reason: an outdated server binary, linked devices turned off on the phone, a session already linked elsewhere, or a QR code that expired before it was scanned.
• Fixed step 4 of the Setup WhatsApp Server window linking to a documentation page that could never open. It now names the file to read in your release ZIP.
• Fixed the menu links on the public About, Privacy and Terms pages doing nothing when clicked. They now take you to the matching section of the landing page.