Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Crypto: The app does not have keys whereas the push extension got them #4074

Closed
manuroe opened this issue Feb 26, 2021 · 0 comments · Fixed by matrix-org/matrix-ios-sdk#1063
Closed

Crypto: The app does not have keys whereas the push extension got them #4074

manuroe opened this issue Feb 26, 2021 · 0 comments · Fixed by matrix-org/matrix-ios-sdk#1063
Assignees
@manuroe
Labels
A-Notifications crypto P1
Milestone
Sprint - Element ...

Comments

@manuroe
Copy link
Member

manuroe commented Feb 26, 2021

There is a failure mode where the push extension gets keys but not the app. The app does not get it from the push extension cache, nor from its own /stream.

The bug may be related to #4073.
@manuroe manuroe added this to the Sprint - Element 1.2.3 milestone Feb 26, 2021
@manuroe manuroe changed the title Crypto: The app can fail to get keys while the push extension got them Crypto: The app does not have keys whereas the push extension got them Feb 26, 2021
@manuroe manuroe self-assigned this Apr 7, 2021
manuroe added a commit to matrix-org/matrix-ios-sdk that referenced this issue Apr 9, 2021
@manuroe
MXBackgroundService: Keep all cached sync responses until there are p…
82a0fbe 
…rocessed by MXSession

element-hq/element-ios#4074

So that we will not lose e2ee keys received by the push extension
@manuroe manuroe mentioned this issue Apr 9, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@manuroe manuroe

Labels
A-Notifications crypto P1
Projects
None yet
Milestone
Sprint - Element 1.3.0
1 participant
@manuroe