-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Labels
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
According to the docs, the Nextcloud max-version is optional for the apps.
Please remove the upper version mandatory constraint.
Ref:
https://docs.nextcloud.com/server/latest/developer_manual/app_development/info.html
for:
https://apps.nextcloud.com/schema/apps/info.xsd
Steps to reproduce
- Create and add a third-party app.
Expected behavior
The nextcloud should check the upper version only if it is defined in the appinfo/info.xml. If it is omitted, then it should not provide an error like:
info.xml did not validate: Element 'nextcloud': The attribute 'max-version' is required but missing., line 32
Nextcloud Server version
30
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?
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
Nextcloud Signing status
Nextcloud Logs
Additional info
Modifying the validator schema is enough?
https://github.com/nextcloud/server/blob/9dbadc5affc7bf47d3c114e5dde539d25ae5ccf6/resources/app-info.xsd#L591