nextcloud / nextcloud/maps

[Bug]: Photos on public shared Maps cannot be displayed

Open
#1,436 0 comments 1 reaction 1 assignee View on GitHub

Nobody has claimed this yet.

0. Needs triage bug feature: 🔗 sharing feature: 🖼 photos
Dominant language
JavaScript
Stars
598
Forks
113
PR merge metrics
No merged PRs in 30d

Description

⚠️ This issue respects the following points: ⚠️
Bug description

Clicking on the preview image triggers two 401 Unauthorized errors:

https://domain.de/index.php/apps/files/api/v1/views
https://domain.de/remote.php/dav/files/undefined/2025_T_0001_NB_IMG_7605.JPG

Opening the photo in the shared folder is working:
https://domain.de/public.php/dav/files/kJBmx3HFyDrmxZS/2025_T_0001_NB_IMG_7605.JPG

Steps to reproduce
  1. Create a shared Link
  2. Copy link "to the map"
  3. Open link in browser
  4. The map is displayed with the preview photos
  5. Click on a preview photo
Expected behavior

The photo should be desplayed in the image viewer

Installation method

None

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 of the server?

None

Is this bug present after an update or on a fresh install of the app?

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

List of activated Apps
Enabled:
  - activity: 4.0.0
  - app_api: 5.0.2
  - bruteforcesettings: 4.0.0
  - calendar: 5.3.8
  - circles: 31.0.0
  - cloud_federation_api: 1.14.0
  - collectives: 3.0.3
  - comments: 1.21.0
  - contacts: 7.2.3
  - contactsinteraction: 1.12.0
  - cookbook: 0.11.3
  - dashboard: 7.11.0
  - dav: 1.33.0
  - deck: 1.15.2
  - drawio: 3.1.0
  - external: 6.0.2
  - federatedfilesharing: 1.21.0
  - federation: 1.21.0
  - files: 2.3.1
  - files_downloadlimit: 4.0.0
  - files_external: 1.23.0
  - files_pdfviewer: 4.0.0
  - files_reminders: 1.4.0
  - files_sharing: 1.23.1
  - files_trashbin: 1.21.0
  - files_versions: 1.24.0
  - firstrunwizard: 4.0.0
  - groupfolders: 19.1.3
  - logreader: 4.0.0
  - lookup_server_connector: 1.19.0
  - mail: 5.1.10
  - maps: 1.6.0
  - metadata: 0.22.0
  - music: 2.2.0
  - nextcloud_announcements: 3.0.0
  - notifications: 4.0.0
  - oauth2: 1.19.1
  - occweb: 0.2.3
  - password_policy: 3.0.0
  - photos: 4.0.0
  - polls: 8.1.4
  - privacy: 3.0.0
  - profile: 1.0.0
  - provisioning_api: 1.21.0
  - quicknotes: 0.8.30
  - recognize: 9.0.3
  - recommendations: 4.0.0
  - related_resources: 2.0.0
  - richdocuments: 8.7.3
  - serverinfo: 3.0.0
  - settings: 1.14.0
  - sharebymail: 1.21.0
  - spreed: 21.1.2
  - support: 3.0.0
  - survey_client: 3.0.0
  - systemtags: 1.21.1
  - text: 5.0.0
  - theming: 2.6.1
  - theming_customcss: 1.18.0
  - twofactor_backupcodes: 1.20.0
  - updatenotification: 1.21.0
  - user_status: 1.11.0
  - viewer: 4.0.0
  - weather_status: 1.11.0
  - webhook_listeners: 1.2.0
  - welcome: 1.3.0
  - whiteboard: 1.1.2
  - workflowengine: 2.13.0
Disabled:
  - admin_audit: 1.21.0
  - encryption: 2.19.0
  - suspicious_login: 9.0.1
  - twofactor_nextcloud_notification: 5.0.0
  - twofactor_totp: 13.0.0-dev.0
  - user_ldap: 1.22.0
Nextcloud Signing status
No errors in log.
Nextcloud Logs

Browser Console
FileSortingConfig.ts:52 
 
 GET https://domain.de/index.php/apps/files/api/v1/views 401 (Unauthorized)
oe	@	FileSortingConfig.ts:52
le	@	FileSortingConfig.ts:31
beforeOpen	@	Viewer.vue:603
openFile	@	Viewer.vue:620
file	@	Viewer.vue:471
Promise.then		
open	@	Viewer.js:331
viewPhoto	@	PhotosLayer.vue:367
onPhotoClick	@	PhotosLayer.vue:363


xhr-request.js:126 
 
 PROPFIND https://domain.de/remote.php/dav/files/undefined/2025_T_0001_NB_IMG_7605.JPG 401 (Unauthorized)
(anonymous)	@	xhr-request.js:126
sB	@	FileInfo.ts:43
request	@	CancelableRequest.js:41
openFile	@	Viewer.vue:651
await in openFile		
file	@	Viewer.vue:471
Promise.then		
open	@	Viewer.js:331
viewPhoto	@	PhotosLayer.vue:367
onPhotoClick	@	PhotosLayer.vue:363
Additional info

The problem exists in v1.4.0 and 1.6.0

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.