Updates

Note: attempting to run this from now on might result in (a direct) ban on your phonenumber of using WhatsApp. The code has not been updated for over a month now, which results in easier detection by WhatsApp.

WhatsSpy Public updates

This page contains notes about how to update a running instance of WhatsSpy Public. This is always relatively easy.

Did you use the Raspberry Pi image installation? No need to update, this will happen automaticlly within 24 hours. HOWEVER: make sure your config.php complies with any changes.

Before/After updating

Shutdown the tracker by using screen -r and then pressing Ctrl+c and Ctrl+a and Ctrl+d.

Apply the update: by following the changelog.

After the update start the tracker again by using screen -r and execute `which php` tracker.php.

Changelog

If you used git (as stated in the getting-started) you can execute cd /var/www/whatsspy/ followed by git fetch --all
followed by git reset --hard origin/master. After this check the changelog notes to comply with config.php changes and restart the tracker again. In case of any errors, first make sure that you have the correct file rights before creating a new issue.

Unlabeled version :

Improved core randomness to prevent automatic WhatsApp ban.

Fixed random disconnects from WhatsApp and increases accuracy of tracker.

🐴Warning: This update contains a database upgrade. This update will happen automatically. If WhatsSpy Public does not work anymore, this is probably a database issue. Check troubleshooting.

🐴Warning 2: The configuration file has changed! Take a look at config.example.php and copy over any missing variables $whatsspyNotificatons (which replaces the old NMA and LN variables) and a new debug option in $whatsappAuth. Make sure you restart the tracker!

Update 1.3.7 : Fixed timezone issue in the statistics page in case PostgreSQL is improperly configured. Also some minor UI fixes. Same rules apply as 1.3.0.

Update 1.3.6 : Fixed several UI bugs (statistics, timeline, new number) as well improved performance in the GUI. Same rules apply as 1.3.0.

🐴Warning: This update contains a database upgrade. This will happen automatically once you open the GUI or start the tracker. In case you get an Database upgrade error you can update the database yourself: