Why history messages are not visible to invited users in encrypted rooms even after settings says it should #5586
Labels
T-Enhancement
New features, changes in functionality, performance boosts, user-facing improvements
Your use case
This issue is a copy of Element-web # 21072. I am asking it here again because this feature is working in Element-web and Element-Desktop but is still not available in Element-ios and Element-android.
Now the question is why this feature is available in Element Web/Desktop and not in Element Mobile. Is there a limitation or is it not possible to share keys from iOS/Android? I am asking this because the product I am planning to develop is a 100% mobile application (at least for now).
Have you considered any alternatives?
No response
Additional context
Original Question from Element-Web vector-im/element-web#21072
Steps to reproduce
Background:
We are trying to implement a mobile app with end-to-end encryption but providing past messages history to new members joining the group is a key thing we need.
Plan:
We were planning to use olm/megolm and matrix-SDK, and then we tried to test our use cases with Element.io (web, desktop, ios, android) versions.
Issue:
History wasn’t available for new users in a room. Since then we have been studying it, the documentation says it should work by sharing keys, but it is not working with Element clients. We have tried all possibilities of inviting a user from different clients and then accepting the invitation from different clients but the new user is either not able to see the history at all or it is broken (like some messages say keys are not shared, or not possible to show).
We are following these issues from different related repositories, they are also talking about similar or same issues and are not able to fix the issue, but we are not sure what are the reasons for not being able to fix/implement this feature of sharing history with new group member by sharing the keys.
element-web#2286
element-web#2713
matrix-react-sdk#5763
Request:
It will be a huge favor if anyone of you can document the reasons why we have not been able to implement this feature till now, what are the issues that even when the client and the documentation say that it should work, it is still broken.
The text was updated successfully, but these errors were encountered: