Change Details

- Migrate native web app -> check if `integrityStore` contains hashes - Reload native web app -> check if hashes are still there - Open web app -> check if initial redux state contained new hashes and that they were added to redux - On both web and native apps -> change thread color and check if the thread hash was updated Log in performance: - iOS emulator takes about 1ms per one thread and the speed should be O(n). In the case from the linear task where the state check took 53s, there was about 2000 threads, so logging in would take additional 2s - Even if we lazily generate the hashes, I don't think there would be a lot of thread updated between logging in and first state check so all that would do is moving the wait time from logging in to the first state check (with a frozen app), so I'm not sure if it's worth it - Web is even faster, ~2000 threads should take about 0.3s

Test: - opening the web page - logging in on web and mobile Check that there are `UPDATE_INTEGIRTY_STORE` actions with batches and the last one with that sets `threadHashingComplete` to true Performance testing: I've let the integrity handler calculate hashes continuously and checked the behaviour of web app and the native app on iPhone X and some old Android. Didn't see any noticeable performance difference when navigating between threads etc.

- Migrate native web app -> check if `integrityStore` contains hashesTest: - Reload nativ- opening the web app -> check if hashes are still therepage - Open web app -> check if initial redux state contained new hashes and that they were added to redux- logging in on web and mobile - On both web and native apps -> change thread color and check if the thread hash was updatedCheck that there are `UPDATE_INTEGIRTY_STORE` actions with batches and the last one with that sets `threadHashingComplete` to true Log in pPerformance:e testing: - iOS emulator takes about 1ms per one thread and the speed should be O(n). In the case from the linear task where the state check took 53s, there was about 2000 threads, so logging in would take additional 2s - Even if we lazily generate the hashes, I don't think there would be a lot of thread updated between logging in and first state check so all that would do is moving the wait time from logging in to the first state check (with a frozen app), so I'm not sure if it's worth it - Web is even faster,I've let the integrity handler calculate hashes continuously and checked the behaviour of web app and the native app on iPhone X and some old Android. ~2000 threads should take about 0.3sDidn't see any noticeable performance difference when navigating between threads etc.