You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some additional information: If I use the file picker of another app, say "Photos", it works absolutely fine.
However, even when logging in with a SAML account, I get a message from the "Photos" app saying "Could not load photos folder", with a similar error message in the Firefox console:
[FATAL] photos: Unexpected Error "Invalid owner type"
Object { app: "photos", uid: "7", level: 2, error: Error }
[ConsoleLogger.js:78:18](webpack:///photos/node_modules/@nextcloud/logger/dist/ConsoleLogger.js)
value ConsoleLogger.js:78
value ConsoleLogger.js:105
n userConfig.js:50
Uncaught (in promise) Error: Couldn't fetch photos upload folder
n userConfig.js:55
Same issue here. Nextcloud Hub 9 (version 30.0.0).
From the dashboard or Photos app, I get the error inside the Console.
userConfig.js:33 [FATAL] photos: Unexpected Error "Invalid owner type" {app: 'photos', uid: '218018', level: '2', error: Error: Invalid owner type
Bug description
I've seen a similar issue here "#45420", and so I will just reference the entire bug thread I have already created here: nextcloud/user_saml#882
I feel as if this could be a problem with NextCloud itself, which is why I am opening a thread here as well. Please advise.
Steps to reproduce
Refer to: nextcloud/user_saml#882
Expected behavior
Refer to: nextcloud/user_saml#882
Nextcloud Server version
29
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.1
Web server
Apache (supported)
Database engine version
MySQL
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
Refer to: nextcloud/user_saml#882
The text was updated successfully, but these errors were encountered: