Change Details

1. Build desktop app connected to your local keyserver. 2. Ensure that olm sessions are present both in MariaDB and IndexedDB. 3. Send some notifications and ensure that `version` field is incremented with each notification. Repeat for both dev and prod (testing for prod will require to remove `isStaffOrDev` condition). It is essential to note that my initial testing plans for the entire e2e MacOS notifications assumed that `NEXT_CODE_VERSION` was temporarily updated to 0 which was the root of the issue this differential resolves. This testing plan assumes that no changes to `NEXT_CODE_VERSION` are done and that it is executed on the master code as it is.

1. Build desktop app connected to your local keyserver. 2. Ensure that olm sessions are present both in MariaDB and IndexedDB. 3. Send some notifications and ensure that `version` field is incremented with each notification. Repeat for both dev and prod (testing for prod will require to remove `isStaffOrDev` condition). Execute similar test for web and native (for native ignore IndexedDB check) in order to test that functionality for this platforms is not broken. It is essential to note that my initial testing plans for the entire e2e MacOS notifications assumed that `NEXT_CODE_VERSION` was temporarily updated to 0 which was the root of the issue this differential resolves. This testing plan assumes that no changes to `NEXT_CODE_VERSION` are done and that it is executed on the master code as it is.

1. Build desktop app connected to your local keyserver. 2. Ensure that olm sessions are present both in MariaDB and IndexedDB. 3. Send some notifications and ensure that `version` field is incremented with each notification. Repeat for both dev and prod (testing for prod will require to remove `isStaffOrDev` condition). Execute similar test for web and native (for native ignore IndexedDB check) in order to test that functionality for this platforms is not broken. It is essential to note that my initial testing plans for the entire e2e MacOS notifications assumed that `NEXT_CODE_VERSION` was temporarily updated to 0 which was the root of the issue this differential resolves. This testing plan assumes that no changes to `NEXT_CODE_VERSION` are done and that it is executed on the master code as it is.