nextcloud / nextcloud/ios

Sharing - Wrong sharing-status after editing file shared by another user [M]

Open
#2,086 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Actions Performed

Preliminaries:
Another @xxx.xx user has shared an image file with you (NOT via link - but shared to you as a @xxxx.xx contact)
This file was shared with the permission to edit the file

  1. Open the app under test
  2. Go to the Files tab (DE: "Dateien")
  3. Identify the file shared with you (see preliminaries)
  4. Tap on the 3-dot-button next to the shared file
  5. Tap "Edit image" (DE: "Bild bearbeiten")
  6. Edit the file (use pencil, draw some lines etc.)
  7. Save the changes - modal should appear: overwrite original file or make a copy?
  8. Select the "overwrite original file" option on this modal (DE: "Original überschreiben")
  9. Inspect the sharing-icon / status next to this file now
  10. Tap the sharing-icon
  11. Try to share this item (create link or share with Telekom contact)

Expected Result
Correct sharing-status. This file was shared by another user. Usually should have the status "Empfangen" (DE) and a cloud-icon with an arrow pointing upwards. This means that this file was shared with me by another user.

Actual Result
Incorrect sharing-status after editing a file shared with me + overwriting the original. The sharing status "Empfangen" (DE) and with the cloud-icon is not displayed. Instead of that, it appears as if this file is not shared at all. If I tap the sharing-button next to it, the sharing window appears. But if I make an attempt to share this file now, I get an error "404: The requested resource could not be found"

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

Reproduce the flow in the iOS app with an image shared by another user: edit it, overwrite the original, and inspect its sharing status and sharing action. Done means the file remains marked as received with the expected cloud icon and sharing it no longer produces a 404 error.

Written by the indexing model from the issue text.

Assessment

Tech stack
swift
Domain
mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.