app_api app got enabled on it's own

[mer-at]

Describe the bug

after upgrading from nextcloud 31 to 32, this app (which i never heard of, nor ever needed) got enabled on it's own and produced errors.
how did it get enabled, and why?
this sounds like mischievous behaviour to me. so i want to know if this behaviour was intentional, and by whom (a legit developer or someone else... ).

Steps/Code to Reproduce

upgrade to nextcloud 32.0.3

Expected Results

no unknown new apps being enabled by someone else

Actual Results

have a new app enabled, by an unknown source, producing errors (or even worse???)

Setup configuration

Nextcloud Hub 25 Autumn (32.0.3)
AppAPI Version 32.0.0

[oleksandr-nc]

Hello,
Just to clarify: the AppAPI app cannot enable itself.

It is possible that AppAPI was already enabled on your Nextcloud 31 instance and only became noticeable after upgrading to Nextcloud 32 because of the errors shown there.
If however AppAPI was disabled on your Nextcloud 31 instance and then became enabled automatically after the upgrade that would indicate a bug in the Nextcloud server-upgrade logic, not in AppAPI itself.

Also note that on new installations, AppAPI is enabled by default unless an administrator explicitly disables it (this is a one-time admin action).

[bwenrich]

AppAPI was included as a default NextCloud app as of v30.0.1 https://docs.nextcloud.com/server/stable/admin_manual/release_notes/upgrade_to_30.html#appapi-app-api-is-now-a-default-app however the check for AppAPI being configured or not wasn't introduced until Nexcloud v32 https://docs.nextcloud.com/server/stable/admin_manual/release_notes/upgrade_to_32.html#appapi-app-api-setup-checks-expanded

The descriptive text and explanations about the meaning of the "error" shown in the administrator's page are also being discussed at #727 - I'd suspect that 99% of people who get this warning will just disable AppAPI instead of bothering to configure it, despite NextCloud raising this as some kind of high-severity problem.

[oleksandr-nc]

Regarding the errors you're seeing - this is a duplicate of #727. The setup check was incorrectly showing as an "error" when no deploy daemon is configured, even though this is optional functionality. We've addressed this by changing the severity from "error" to "info", so it will no longer appear as an alarming error message.

If you don't plan to use External Apps (ExApps), you can safely ignore the info message or disable the AppAPI app entirely in your apps settings.

Closing this as a duplicate of #727. Thank you for the feedback!