[Bug]: federated shared file still in "waiting"
Open
Nobody has claimed this yet.
0. Needs triage
28-feedback
bug
feature: federation
feature: sharing
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
Files are still in "waiting" state, this is a bug that occurs only when it is a federated share.
Steps to reproduce
- on instance B with user B, configure a folder for incoming shares in your personal settings, for example "/Shares"
- from instance A and user A, create a file and share it to user B on instance B
- log on instance B with user B, accept the incoming federated share from user A.
- navigate into the /Shares folder, you should see the file, and you can open it
- now go to "Shared with me" tab, you can see the file, however, when you click on it, Nextcloud goes directly back to All Files.
Expected behavior
No state
Nextcloud Server version
28
Operating system
None
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
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 or test is identified in the issue. Start by reproducing the federated-share workflow between instances A and B, then inspect the server handling of the Shared with me entry and relevant logs; done means the shared file no longer remains in a waiting state or redirects to All Files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100