Provide a different response when E2EE is enabled and app is too old
Open
Nobody has claimed this yet.
bug
Needs triage
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 17h 55m
- Merged PRs (30d)
- 350
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Ref https://help.nextcloud.com/t/nextcloud-talk-ios-outdated/220335
The iOS app and the android app both show the "App is outdated" screen when E2EE call encryption is enabled. We should think about providing context, or (IMO the better option), just block joining/starting calls, as chatting would still work fine.
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
No source file, test, or entry point is named. Read the linked forum discussion and trace how outdated iOS and Android apps behave when E2EE is enabled; clarify whether the intended result is added context or blocked call actions. Done means the chosen behavior is implemented while chatting remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- mobile, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100