[Bug]: 3rd party app breaks entire appstore
Nobody has claimed this yet.
- 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
the 3rd party app allinoneaccessibility from skynettechnologies breaks my entire app store in my nextcloud instance, although i have not installed the app, no other app can be viewed/installed/enabled/disabled in the appstore anymore, a misconfigured app should not be able to break the whole appstore
there is already a issue created at the devs repository of the nextcloud app:
https://github.com/skynettechnologies/skynettechnologiesallinoneaccessibility/issues/3
Steps to reproduce
- install/update nextcloud server 34.0.1
- go to apps
- error message "app list can not be loaded, try again later", no apps are shown
Expected behavior
appstore is working correctly, the misconfigured app should not be listed in the appstore
Nextcloud Server version
34
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.4
Web server
Apache (supported)
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?
Encryption is Disabled
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
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 files or tests are named. Start by reproducing the failure on Nextcloud Server 34.0.1 with the referenced third-party app present, then inspect the app-store error and server logs to locate the failing boundary. Done means the app store can list, install, enable, and disable apps despite the misconfigured app.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100