matrix-org / matrix-org/matrix-rust-sdk
Group Session Cache inconsistency between IOS main app and Share Extension
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.3k
- Forks
- 500
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 106
Description
In Element/IOS the encryption is used by the main app and the Share extension running as different processes. This leads to reproducible inconsisteny of the message ID (and I fear sometimes also of the session ID) by using the group session cache.
I've files the bug as https://github.com/vector-im/element-ios/issues/7499 and user @Anderas did a great analysis what's happening.
I have a slight feeling that the root issue might be in the cache handling in this SDK (cache is maybe not multi-process-proof), therefore I file this issue here as well.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked Element iOS report, vector-im/element-ios#7499, and the referenced analysis of the Group Session Cache inconsistency. Reproduce the message ID mismatch between the main app and Share Extension processes, then inspect the SDK's cache handling for multi-process behavior. Done means the cross-process cache behavior is understood and the reported inconsistency is resolved or clearly bounded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100