1. Use query to check notifications session for multiple devices at once and initilize crypto account in send utils instead of each time before encryption. it is huge performance improvement.
2. Fix context cycle

Add additional method to check for presence of notifications session for multiple devices with one db query

Address review

Address review

Addres review

Address review

Address review

Address review

Address review

Address review

Address review

Address review

In D12692#361481, @kamil wrote:

Right now two JS threads (shared worker and service worker) can concurrently modify the same key in IndexedDB. I think to make it safe we should use transactions to make sure this is safe.

Unfortunately, looks like locaforage is not supporting this: https://github.com/localForage/localForage/issues/582 and https://github.com/localForage/localForage/issues/17.

Could you do some research about whether it's safe or suggest an alternative solution?

(this could change most of the code so not reviewing details of this diff)

About to create fork with PR shortly

In D12677#361397, @bartek wrote:

The HTTP request-response logic looks good; it's analogous to the existing Blob GET request logic.

Accepting but please remember to fix that semicolon. Otherwise, release builds will fail.

In D12668#361448, @ashoat wrote:

In D12668#361372, @kamil wrote:

I really don't like the idea (looking at this diff and the entire stack) of passing isKeyserverSession - notification crypto module should treat all devices the same regardless of whether this is a keyserver or client device, and we should only have senderID, because the current design makes it confusing. But given this is implemented and tested I believe we can proceed, you could create a follow-up task to improve it in future but for now LGTM.

Curious for @marcin's perspective on this, and how much time it might take to fix up

Rebase

Use common C++ implementation on Android. It was tested the same way as iOS using latest staging Tunnelbroker release

Rebase

Use the API in send-utils

Make encryptNotification a part of olmAPI. This change is ESSENTIAL on web since it makes encryptNotification run on shared worker. This enables us to deterministically handle race conditions.

Improvement: use the same functions to fetch and persist olm data regardless of notification type (keyserver/peer device)

Use transactional write when creating outbound session

A couple of changes

If the patch file appears cumbersome to review I will create fork of localforage with PR containing those changes.

Rebase before landing

Rebase before landing

Rebase before landing

Log information about notification encryption failure regardless of user staff member status.

Remove TODO

Fix race condition by exposing olm session creation via context

Add error handling to CommCoreModule::isContentSessionInitialized

Rename ...DataContent... -> ...Data... to remove confusion around Conent keyword when dealing with notifs sessions

Rebase before landing

rebase before landing

Address Varun's and Will's feedbacks

This function is supposed to be used exclusively with thick threads.

1. Don't pass references to unique pointer between lambdas - a rookie mistake!. Pass shared pointers by copy.
2. Switch to multi process mode on MMKV on Android

In D12695#360306, @ashoat wrote:

Hey @marcin, any reason this hasn't been landed yet?

Rebase before landing