photos icon indicating copy to clipboard operation
photos copied to clipboard

Photos v32.0.1 introduces issue navigating next/previous images in file viewer

Open valdearg opened this issue 1 month ago • 21 comments

Describe the bug When in the file viewer, clicking on next/previous buttons has no effect.

To Reproduce Steps to reproduce the behavior:

  1. Go to a folder in file viewer
  2. Click on picture in folder with multiple images.
  3. Click next or previous.

Expected behavior Next/previous image should show.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [e.g. iOS] Windows 11
  • Browser [e.g. chrome, safari] Firefox
  • Version [e.g. 22] 144.0

Browser log


On opening the image:

File info for /Photos/Instagram (Raider)/asami_gate/1393672786.666498095246234917.jpg fetched 
Object { filename: "/Photos/Instagram (Raider)/asami_gate/1393672786.666498095246234917.jpg", basename: "1393672786.666498095246234917.jpg", lastmod: "Mon, 19 Jul 2021 23:04:53 GMT", size: 106714, type: "file", etag: "f08c7fee7e5e487acb0186fc3d77682e", mime: "image/jpeg", tags: "", getcontentlength: 106714, getcontenttype: "image/jpeg", … }
Viewer.vue:669:1

Could not open file /Photos/Instagram (Raider)/asami_gate/1393672786.666498095246234917.jpg TypeError: can't access property "filename", a is undefined
    currentIndex Viewer.vue:802
    openFileInfo Viewer.vue:802
    openFile Viewer.vue:670
    file Viewer.vue:460
    VueJS 11
    open Viewer.js:313
    $5 viewerAction.ts:82
    execDefaultAction FileEntryMixin.ts:327
    click FileEntry.vue:5
    VueJS 33
Viewer.vue:681:1

Then when clicking on the next button:

TypeError: can't access property "mime", e is undefined
    openFileFromList Viewer.vue:820
    next Viewer.vue:1087
    VueJS 4
    next NcModal.mjs:432
    VueJS 4
vue.runtime.esm.js:3065:17

valdearg avatar Oct 27 '25 23:10 valdearg

Have the same problem with a complete new installation from scratch. No addons activated so far. In the Photos-App the buttons work, in file viewer it is not working, also the Autoplay Button. Tested with Firefox and Google-Chrome

svenhardwarepunk avatar Oct 28 '25 08:10 svenhardwarepunk

Found out, that it is only not working if I'm logged in. If I share a public link of the folder, there it is working fine.

svenhardwarepunk avatar Oct 28 '25 08:10 svenhardwarepunk

Same here, tested under Ubuntu 22.04 and lmde7, various browsers.

resoli avatar Oct 28 '25 11:10 resoli

i can confirm this bug with Nextcloud 31.0.10.

jolang avatar Oct 28 '25 22:10 jolang

Same Problem here on Nextcloud 31.0.10 but bug active since around 24.09.2025 so more versions should be affected.

Also the bug also disappears here when accessing the gallery through a public link.

R053NR07 avatar Oct 29 '25 13:10 R053NR07

I am experiencing the same issue with media scrolling directly in the browser.

Initially, I cleared the browser cache (Brave), but it did not resolve the problem. Then I tested on another computer using a different browser (Edge), and the issue persists.

On the server, I cleared the cache, applied all available updates, and restarted the system. Despite this, the problem continues on this version.

Nextcloud information:

Nextcloud installed: true
Version: 32.0.1.2
Version string: 32.0.1
Edition: -
Maintenance mode: false
Database upgrade needed: false
Product name: Nextcloud
Extended support: false

Server information:

NAME="Ubuntu"
VERSION="20.04.6 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.6 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

Kernel information:

Linux @@@@.@@@@@@@.@@@.@@ 5.4.0-216-generic #236-Ubuntu SMP Fri Apr 11 19:53:21 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux

PHP information:

PHP 8.3.20 (cli) (built: Apr 10 2025 21:33:00) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.3.20, Copyright (c) Zend Technologies
    with Zend OPcache v8.3.20, Copyright (c), by Zend Technologies

Database information:

mysql Ver 15.1 Distrib 10.6.22-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2

Photos app version:

5.0.0-dev.1

brunoandradeSP avatar Oct 29 '25 17:10 brunoandradeSP

Same here with NC 32.0.1. But I don't think, that this is a problem of the Photos app. I think this is a Problem in Nextcloud Viewer.

Could not open file /path/to/file.jpeg TypeError: can't access property "filename", a is undefined currentIndex Viewer.vue:802 openFileInfo Viewer.vue:802

BKapelari avatar Oct 29 '25 18:10 BKapelari

Same here with NC 32.0.1. But I don't think, that this is a problem of the Photos app. I think this is a Problem in Nextcloud Viewer.

Could not open file /path/to/file.jpeg TypeError: can't access property "filename", a is undefined currentIndex Viewer.vue:802 openFileInfo Viewer.vue:802

I encountered an issue in the Nextcloud Viewer where it fails to open some files. According to the browser console output, it seems that the Viewer is trying to access properties of a file that does not exist in the internal loaded file list, which results in a TypeError when reading filename or mime.

Console output:

TypeError: Cannot read properties of undefined vue.rintime.esm.js:3065
(reading 'mime')
at r. openFileFromList (Viewer.vue: 820:1)
at r.next (Viewer.vue:1087:1)

I plan to try regenerating thumbnails and updating the file index to see if the issue persists.

brunoandradeSP avatar Oct 29 '25 19:10 brunoandradeSP

I plan to try regenerating thumbnails and updating the file index to see if the issue persists.

I did this already - no change. Nextcloud 32.0.1 as well here. My test environment with Nextcloud 32.0.0 works fine though.

And yes, it is not the Photos app but the viewer in the Files app - which is still available, even if the Photos app is disabled.

arnowelzel avatar Oct 29 '25 21:10 arnowelzel

The issue nextcloud/viewer#2990 was already fixed with pull request nextcloud/viewer#3005 and backported to all supported stable releases:

  • nextcloud/viewer#3007
  • nextcloud/viewer#3008
  • nextcloud/viewer#3009

jolang avatar Oct 30 '25 01:10 jolang

The issue nextcloud/viewer#2990 was already fixed with pull request nextcloud/viewer#3005 and backported to all supported stable releases:

When will the update arrive on stable for 32.0.1? Since I did not get any update so far and it is still broken on my side on all 3 nextcloud ikstances.

SeDi343 avatar Nov 07 '25 11:11 SeDi343

If it's any help to anyone, if you're running baremetal (not docker), you can run the following (as root):

cd /var/www/nextcloud/apps/
mv viewer/ /tmp/viewer-v32.0.1
git clone https://github.com/nextcloud/viewer.git
cd viewer/
git switch stable32
npm ci
npm run build
cd ..
chown -R www-data:www-data viewer/

Please note, running this will temporarily take your Nextcloud site offline.

This will basically make a backup of the current Viewer app version, then clone down the Viewer repo, switches to the latest stable branch, builds everything.

Once run, go back to your Nextcloud and CTRL+F5 to refresh the page without cache. It takes a moment the first time you switch between images but it works.

valdearg avatar Nov 07 '25 19:11 valdearg

The issue nextcloud/viewer#2990 was already fixed with pull request nextcloud/viewer#3005 and backported to all supported stable releases:

When will the update arrive on stable for 32.0.1? Since I did not get any update so far and it is still broken on my side on all 3 nextcloud ikstances.

This is not an official statement. I think we will have to wait until the next round of stable milestones is released, which currently scheduled for November 20.

jolang avatar Nov 10 '25 01:11 jolang

By the way: the build of the viewer warns about a deprecated API:

https://sass-lang.com/documentation/breaking-changes/legacy-js-api/

arnowelzel avatar Nov 10 '25 08:11 arnowelzel

same problem here for some weeks... any update on the fix via update?

fschiefenhoevel avatar Nov 18 '25 13:11 fschiefenhoevel

same problem here for some weeks... any update on the fix via update?

There's an RC1 release if you care to live on the wild side. Full release shouldn't be too long afterwards.

Unfortunately due to how NC is developed it seems that core apps will be updated in line with the main product, so the developer wouldn't release just an update to Viewer for example.

valdearg avatar Nov 18 '25 19:11 valdearg

same problem here for some weeks... any update on the fix via update?

There's an RC1 release if you care to live on the wild side. Full release shouldn't be too long afterwards.

Unfortunately due to how NC is developed it seems that core apps will be updated in line with the main product, so the developer wouldn't release just an update to Viewer for example.

thanks for the info! I think I can wait a little longer :-)

fschiefenhoevel avatar Nov 18 '25 19:11 fschiefenhoevel

If it's any help to anyone, if you're running baremetal (not docker), you can run the following (as root):

cd /var/www/nextcloud/apps/
mv viewer/ /tmp/viewer-v32.0.1
git clone https://github.com/nextcloud/viewer.git
cd viewer/
git switch stable32
npm ci
npm run build
cd ..
chown -R www-data:www-data viewer/

Please note, running this will temporarily take your Nextcloud site offline.

This will basically make a backup of the current Viewer app version, then clone down the Viewer repo, switches to the latest stable branch, builds everything.

Once run, go back to your Nextcloud and CTRL+F5 to refresh the page without cache. It takes a moment the first time you switch between images but it works.

Thank you very much @valdearg It worked for me !

MarkoAmb avatar Nov 20 '25 01:11 MarkoAmb

Issue resolved with latest update to 32.0.2

SeDi343 avatar Nov 22 '25 12:11 SeDi343

Just pulled the latest docker image and can confirm it fixed the issue for me. Appreciate the fix and all the hard work done on this awesome project. Thank You!

Spajderix avatar Nov 22 '25 20:11 Spajderix

I just updated my instance (non-docker) to 32.0.2 and can confirm that the issue is fixed.

lsr-dev avatar Nov 22 '25 22:11 lsr-dev