[Bug]: PWA (when installed from login screen) - force renamed to 'Nextcloud' instead of custom server name

⚠️ 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

After awaiting release of 32.0.1 due to other PWA issue being resolved... I setup 32.0.1 on two of my Nextcloud instances.

Both of them, I install as a PWA on my desktop machines, as my preferred setup. I do this from the login page, so that they are installed as an 'overall PWA' instead of a PWA for any internal app on the cloud...

However, upon doing this in version 32.0.1, both of my previously working overall PWAs automatically renamed themselves to 'Nextcloud' instead of the custom server name (i.e. 'crowetic cloud' ) that they were previously. This is quite annoying, especially to someone like me that runs multiple nextcloud instances, having them all setup as overall PWAs, then having them all rename themselves to 'Nextcloud' makes it very difficult for me to keep track of the apps...

In versions prior to 32, all PWAs installed from the login screen worked perfectly, and would be named correctly as the server name (I.E. 'crowetic cloud' )... Now, all of them auto-rename themselves to 'Nextcloud' making it very difficult to distinguish between them installed on the system.

They also want to change the icon to the default nextcloud icon instead of the custom favicon of the instance...

Both of these issues are very annoying, and are preventing me from updating my other instances, as it completely kills my workflow and delays my productivity having to open them to realize which instance they belong to, all of them with the same name and logo.

Steps to reproduce

1. Run a version under 32, and have the instance themed with a name and custom favicon
2. Install a PWA from the primary login screen (before authentication) - This will install what I call an 'overall PWA' for the cloud instance, and not for an app inside the cloud.
3. Update to version 32.0.1 - After the update, open the PWA, and it will auto-rename, and auto-change the favicon to the default Nextcloud name and logo.

Expected behavior

The expected behavior should be what it was on all updates prior, the PWA installed from the login screen should have the icon and name of the instance, and keep it after the update.

Nextcloud Server version

32

Operating system

Debian/Ubuntu

PHP engine version

PHP 8.3

Web server

Apache (supported)

Database engine version

PostgreSQL

Is this bug present after an update or on a fresh install?

Upgraded to a MAJOR version (ex. 31 to 32)

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

Will add this if needed, but it happened on both of my instances, with or without any specific app enabled, and I doubt the server config has anything to do with it.

List of activated Apps

I will provide this if needed, but again this happens with or without any or all apps enabled/disabled.

Nextcloud Signing status

Nextcloud Logs

Additional info

I will provide other information if required, but I don't think it should be needed.

The relevant entry point is the primary login screen's PWA installation flow; reproduce it with a themed pre-version-32 instance, then upgrade to 32.0.1 and compare the installed name and favicon. No source file or test is identified in the report. Done means login-screen PWAs retain the instance's custom name and favicon after the upgrade.