nextcloud / nextcloud/spreed

File cannot be opened directly after sharing

Open
#16,828 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug feature: frontend 🖌️ feature: upload & shares & voice 📤🎙️ regression
Dominant language
JavaScript
Stars
2.2k
Forks
586
Avg merge
18h 27m
Merged PRs (30d)
333

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.

Steps to reproduce

  1. Share a screenshot (via CMD+V in case that matters) in Talk
  2. Try to open the image, after uploading was successful
Expected behaviour

Image should open

Actual behaviour
Image

URL is
remote.php/dav/files/uid/Filename.png

instead of

remote.php/dav/files/uid/Talk/Filename.png

Which sounds like we are using the path from the last message, which is allowed to not have the full path? Or maybe a downside of HPB Relay?

Full reload and retrieving messages via context endpoint makes the file accessible again (sometimes? Not fully sure).
Could also be a files bug of course.

Talk app

Talk app version: stable33

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 reproducing the upload-and-open flow in Talk app stable33, then compare the immediate message with the result after a full reload or context-endpoint retrieval. Trace why the generated remote.php/dav/files/uid/Filename.png URL omits the Talk path, including whether HPB Relay is involved; done means the shared image opens immediately with the correct path and the behavior is covered by a regression test.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.