@O3car can you elaborate on that?
New app update (
TEST: 3.0.2):
Big stability release. Updated to the final WhatsApp SDK release candidate (rc10) ā first SDK update since November, packs 5+ months of upstream work. Combined with internal fixes targeting the high-CPU and āfuture messagesā crashes some of you have been reporting since last releases.
Changelog:
NEW:
1: NEW: WhatsApp SDK update to 7.0.0-rc10 (final release candidate)
2: MAJOR: Update app to NodeJS 22 (requires Homey v12.9.0+)
3: Memory improvements, prevent app to crash on load. Cache became to big and caused CPU/RAM issues (going back to version 1.39.2 only possible with repair)
4: Add new condition flowcard - Text Starts With ā¦FIXES:
1: FIX: high CPU usage and crashes caused by āfuture messagesā pile-up
2: FIX: reconnect storms with overlapping reconnect attempts
3: FIX: device store filling up over time
4: FIX: 30 second delay on sending messages when the device was reconnecting
5: FIX: stale state surviving a logged-out / clear-session event
6: FIX: infinite query timeout causing memory growth
7: FIX: pre-key cleanup at startup could crash on installs with very large stores
8: FIX: parsing LID to phonenumber (SDK v7) (phonenumbers were encrypted this fixes it)
9: FIX: Poll card now only has 2 required items
10: FIX: Pairing issues
11: FIX: Text condition
12: FIX: reply Code token (due to LID parsing this got corrupted)
If you find any issues, send a diagnostic report
Note: Before sending a report make sure to reproduce the issue so the issue will be visible in the report
Via Homey Mobile app:
More - apps - WhatsApp - settings wheel right top - send diagnostic report (put your email in the input field to make it easier)
Via Homey Webapp:
Settings wheel bottom left - Select WhatsApp - Click on send diagnostic report
You can install this version by clicking the link above and press install (do not remove the app, only press install)
Donāt want to be part of a test version? Install the live version ā WhatsApp | Homey
@O3car I could reproduce, see fix above
Wanted to wait for the LIVE version, but couldnāt stand the constant crashes so updated to TEST anyways. Unfortunately the app still crashes for me⦠![]()
Diagnostic: 7f3b4d32-a9eb-4ea7-b9fd-c9fa3a14c1c0
Trying to repair my second whatsapp device, maybe thatās the source of the crash. Tried it again and instantly crashed:
cc2d1972-ed2b-49ac-9528-f8c3f3fa7014
Edit: now managed to update both the devices, and they both seemed to work. But still regular app-crashes unfortunately. I have 360mb of memory free. Could that be the issue?
report: 921d5860-24fb-41d3-87e4-80b4b20b0bf7
@Daan_Dagevos thanks ! Will check
During startup thereās a migration to change the save location for sessions
Also this means that going back to live version requires a repair
In case you wanted to do that
For now no reason to go back. Iāve got the issues in both versions ![]()
But thanks! Hope thereās a fix!
@Daan_Dagevos yeah a similar issue I didnāt expect to see
Will check with maintainer of library
Session error:SessionError: Over 2000 messages into the future!
Anyone experiencing this�
Iām trying to automatically send my daughter a joke of the day. She gets a message saying thereās a message incoming and it shows my end with single tick. Never resolves itself so I end up copying and pasting the message and sending manually.
Any ideas?
@Casper181 which app version?
1.39.2
New app update (
TEST: 3.0.4):
Big stability release. Updated to the final WhatsApp SDK release candidate (rc10) ā first SDK update since November, packs 5+ months of upstream work. Combined with internal fixes targeting the high-CPU and āfuture messagesā crashes some of you have been reporting since last releases.
Changelog:
NEW:
1: NEW: WhatsApp SDK update to 7.0.0-rc10 (final release candidate)
2: MAJOR: Update app to NodeJS 22 (requires Homey v12.9.0+)
3: Memory improvements, prevent app to crash on load. Cache became to big and caused CPU/RAM issues (going back to version 1.39.2 only possible with repair)
4: Add new condition flowcard - Text Starts With ā¦FIXES:
1: FIX: high CPU usage and crashes caused by āfuture messagesā pile-up
2: FIX: reconnect storms with overlapping reconnect attempts
3: FIX: device store filling up over time
4: FIX: 30 second delay on sending messages when the device was reconnecting
5: FIX: stale state surviving a logged-out / clear-session event
6: FIX: infinite query timeout causing memory growth
7: FIX: pre-key cleanup at startup could crash on installs with very large stores
8: FIX: parsing LID to phonenumber (SDK v7) (phonenumbers were encrypted this fixes it)
9: FIX: Poll card now only has 2 required items
10: FIX: Pairing issues
11: FIX: Text condition
12: FIX: reply Code token (due to LID parsing this got corrupted)
13: FIX: issue where loaded state was too old and instance tries to load 2000+ messages which are no longer relevant
If you find any issues, send a diagnostic report
Note: Before sending a report make sure to reproduce the issue so the issue will be visible in the report
Via Homey Mobile app:
More - apps - WhatsApp - settings wheel right top - send diagnostic report (put your email in the input field to make it easier)
Via Homey Webapp:
Settings wheel bottom left - Select WhatsApp - Click on send diagnostic report
You can install this version by clicking the link above and press install (do not remove the app, only press install)
Donāt want to be part of a test version? Install the live version ā WhatsApp | Homey
@Daan_Dagevos please see release above, which contains a fix for your error. Hope that resolves it. Let me know ![]()
Sounds promising! Iām currently in the middle of migrating a 2023 to a 2026 (what a headache..!). But will test once itās finished ![]()
Iām at 3.0.5 now. Is that an even newer test version? Iāve reconnected and it seems to work flawlessly so far. Will keep you updated ![]()
(migrating from 2023 to 2026 only works well when youāre doing a USB backupā¦)
@Daan_Dagevos yes, 3.0.4 had a small bug, so 3.0.5 is the same without the bug ![]()
@martijnpoppen Iām now getting āwaiting for this messageā in whatsapp. Any idea where this came from?
bbdfcc18-6457-4955-be37-46149ea5d60f
@Daan_Dagevos yes I do, Iā'll check. I removed functionality because the SDK should handle this. Probably not.. ![]()
Sorry ive been away.
Test version was worse for me, it would not add at all so I reverted to the original which did allow me to link.
It linked correctly but wont refresh and now when a message sends the receiver gets a message to say āwaiting for this message, this may take a whileā
Today i reinstalled and it back up and running
I will see if it times out again and create a ticket and try test version again.
Thanks
@Welshsmarthome ok thats fine. At some point the test version will become the Live version, so itās good to see the issues before that. Let me know if you want to try out the test version again
