Localized ExApp names are stored as Array during update #1175

Description

Updating an ExApp whose metadata contains multiple localized <name> elements resulted in its registered name and container display-name environment variable being set to the literal string Array.

The affected ExApp remained enabled and its backend responded after the update. This report concerns the name handling and PHP warnings; no impact on search or indexed data was established.

Environment

• Nextcloud: 35.0.2
• AppAPI: 35.0.0
• ExApp: Findling Backend, updated from 1.5.1 to 1.6.0
• Deployment: AppAPI with HaRP

Observed behavior

During the native ExApp update, two PHP warnings reported Array to string conversion:

• lib/public/AppFramework/Db/Entity.php, line 142
• apps/app_api/lib/DeployActions/DockerActions.php, line 1108

After the update:

• The AppAPI registration returned the ExApp name as the string Array.
• The running container had APP_DISPLAY_NAME=Array.
• The ExApp version was 1.6.0 and it remained enabled.

The previous container already had APP_DISPLAY_NAME=Array, so this is not necessarily new in Findling 1.6.0. The registration name before the update was not independently verified.

Metadata involved

The Findling Backend 1.6.0 metadata contains three localized name elements, each with the same display text:

<name>Findling Backend</name>
<name lang="de">Findling Backend</name>
<name lang="fr">Findling Backend</name>

The candidate metadata observed by AppAPI represented name as an array of three values. The installed AppAPI update path passes that value to the ExApp name setter and casts it to a string when building deployment parameters. This is a plausible explanation for the warnings and resulting value, but it has not been reproduced with a minimal independent ExApp.

Expected behavior

The registration and APP_DISPLAY_NAME should contain an appropriate display name, such as Findling Backend, without array-to-string warnings.

Additional context

This resembles #969 in that XML metadata is represented as an array and later converted to a string. However, #969 concerned an empty environment-variable default; this report concerns multiple localized ExApp name elements.

No fresh installation or additional update was performed solely to reproduce this issue.