nextcloud / nextcloud/ios

E2EE broken when using share extension

Open
#3,775 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Swift
Stars
2.5k
Forks
1k
Avg merge
2d 18h
Merged PRs (30d)
13

Description

See https://github.com/nextcloud/ios/issues/3699 which has been closed without being confirmed it is actually fixed - which is not the case (!).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked issue #3699 and reproducing the E2EE failure through the iOS share extension. No file or test is named in this report, so locate the share-extension entry point and related encryption flow before investigating. Done means shared content remains end-to-end encrypted and the earlier regression is covered by a verified test or reproduction.

Written by the indexing model from the issue text.

Assessment

Tech stack
swift
Domain
mobile, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.