-
Notifications
You must be signed in to change notification settings - Fork 39
fix: fetch MLS public keys the same way as feature config [WPB-17161] #3991
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
saleniuk
wants to merge
36
commits into
develop
Choose a base branch
from
fix/fetch-mls-public-keys-on-foreground
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+29
−5
Open
Changes from all commits
Commits
Show all changes
36 commits
Select commit
Hold shift + click to select a range
0a20227
chore: disable picture in picture
MohamadJaara 478667b
fix: broken test for AnonymousAnalyticsManagerTest
yamilmedina 5f4ebf7
fix: broken class ExternalLoggerManager for flavor
yamilmedina af6cb19
fix: broken tests for flavored runs
yamilmedina ca62a1a
fix: disable in-call reactions while connecting [WPB-16372] (#3916)
saleniuk 63637e3
fix: crashes on audio message playback [WPB-16195] (#3917)
saleniuk a6254ef
chore: run connected tests on dev flavour [WPB-16596] (#3925)
MohamadJaara a57eadc
fix: persist self email to register device with 2fa [WPB-16573] (#3929)
saleniuk 2166088
chore: update kalium
MohamadJaara 63a7f60
fix: app crashing when sharing location form a modified version of an…
MohamadJaara 0fe8ab1
fix: analytics should be disabled for c-builds (WPB-16675) (#3940)
yamilmedina b843e93
fix: handle 2fa on RegisterDeviceScreen [WPB-16573] (#3934)
saleniuk e0fce29
chore: update kalium
MohamadJaara e6bc0f6
chore: release notes for 4.11.0
MohamadJaara 4cf7ca3
fix: compare versions in the build script
MohamadJaara 5c4e3d8
chore: bump version to 4.11.1
MohamadJaara 42e658b
chore: update kalium
MohamadJaara 073894e
fix: prod builder script not running
MohamadJaara d8912c3
fix: prod builder script not running
MohamadJaara 360acc6
fix: prod builder script not running
MohamadJaara add996f
feat: database optimizer [WPB-16842] (#3950)
Garzas 58ae553
fix: audio recording and playing crashes [WPB-16687] [WPB-16835] (#3955)
saleniuk 64909ed
Revert "chore: bump version to 4.11.1"
MohamadJaara 5d77493
chore: bump upload artifact action
MohamadJaara 5e618ca
chore: bump version to 4.11.1
MohamadJaara 00c3613
fix: make sure coroutine is init before using it on analytics manager…
yamilmedina 075cb91
test: speed up tests [WPB-8645] (#3964)
vitorhugods 3a369c8
chore: update kalium
saleniuk 7601617
chore: bump core crypto to 3.1.1
MohamadJaara e763dff
fix: fetch MLS public keys the same way as feature config [WPB-17161]
saleniuk 57ef726
Merge remote-tracking branch 'refs/remotes/origin/release/candidate' …
saleniuk 8aea3d5
Merge remote-tracking branch 'origin/develop' into fix/fetch-mls-publ…
saleniuk 443d4ef
Merge remote-tracking branch 'origin/develop' into fix/fetch-mls-publ…
saleniuk 7fee3f7
update kalium ref
saleniuk 61c08a3
remove code added improperly during merge
saleniuk 9afe3ae
Merge remote-tracking branch 'origin/develop' into fix/fetch-mls-publ…
saleniuk File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Submodule kalium
updated
8 files
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am pretty sure this whole block of
runSyncTasks()
here was just a quick hack and now it is getting expanded further.App knows too much about this.
We should either:
A. Launch
mlsPublicKeysSyncWorker
whenUserSessionScope
starts, and have it wait for Sync to be LIVE before doing anything else. Once LIVE it will do its thing, be it on the background or not. And it can reschedule itself to repeat every 24h if still running.B. Create a
ForegroundWorker
of some sorts in Kalium, so the app would call it and Kalium would take over.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vitorhugods should I do it as part of this ticket or should we create a dedicated one to clear this up?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The documentation states that it should be called each time the user puts the app in the foreground, so running it each time the app becomes LIVE is not exactly the same.
And it actually waits until live when being executed, this logic is implemented already inside this worker, just like for feature flag sync worker and proteus sync worker.
About B idea, I don't know if I get it correctly but the only change would be that the app starts this single
ForegroundWorker
instead of starting each one separately?