Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inside details of a file, activities view is broken #12647

Closed
4 tasks done
juanyunis opened this issue Mar 4, 2024 · 1 comment
Closed
4 tasks done

Inside details of a file, activities view is broken #12647

juanyunis opened this issue Mar 4, 2024 · 1 comment
Labels

Comments

@juanyunis
Copy link

⚠️ Before posting ⚠️

  • This is a bug, not a question or an enhancement.
  • I've searched for similar issues and didn't find a duplicate.
  • I've written a clear and descriptive title for this issue, not just "Bug" or "Crash".
  • I agree to follow Nextcloud's Code of Conduct.

Steps to reproduce

  1. Open NextCloud Android apl
  2. Select any file and click the 3 dots at the right side
  3. Select Details
  4. Details is stuck like loading but it is not, and I don't see a url call to the server for that.

Expected behaviour

Like web, it should list all the activities related to that file.

Actual behaviour

I can't see any activities of a file when I click Details of any file.
Screenshot_20240304_150212_Nextcloud
Screenshot_20240304_150222_Nextcloud
Screenshot_20240304_150225_Nextcloud
Screenshot_20240304_150229_Nextcloud

And this is in the web version, it does work.
20240304_152426

Android version

14

Device brand and model

Samsung Galaxy S24 Ultra 5G (SM-S928U1)

Stock or custom OS?

Stock

Nextcloud android app version

3.28.0

Nextcloud server version

28.0.3

Using a reverse proxy?

Yes

Android logs

No response

Server error logs

No response

Additional information

No response

@juanyunis juanyunis added the bug label Mar 4, 2024
@joshtrichards
Copy link
Member

3.28.0

We know about this one, but thanks for reporting nonetheless!

You had me worried for a moment because I was certain we'd already fixed this. It is fixed in our dev builds. It appears it was merged, but is set for release in v3.28.1 via #12541. It just didn't make it in time for v3.28.0.

Duplicate of #12364

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants