[Bug]: Force reload required after upgrade 29 -> 30

[SystemKeeper]

⚠️ 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 upgrading from 29.0.4 to 30.0.0 Beta 3 a force reload was required on the users end (multiple apps were affected, like talk, forms,…). Seems that our cachebuster has an issue somewhere?

Steps to reproduce

1. Upgrade from 29 to 30

Expected behavior

No force reload required

Installation method

None

Nextcloud Server version

master

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

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

[juliusknorr]

Not entirely sure if that is the cause but could contribute to it: nextcloud-libraries/nextcloud-vite-config#267

[sorbaugh]

Can you please look @susnux 🙏

[sorbaugh]

Proposed way forward by @nickvergessen if I understood correctly: Check if it's a shipped app and additionaly use the Nextcloud Version to create a new hash.

[susnux]

So some background:

There was a bug in nextcloud-vite config, this now fixed. All apps that updated to v1.4.2 or later should work correctly.
But there is still a problem for shipped apps like the viewer if their version number does not change -> same cache buster.

[nickvergessen]

But there is still a problem for shipped apps like the viewer if their version number does not change -> same cache buster.

That's where:

Check if it's a shipped app and additionaly use the Nextcloud Version to create a new hash.

would come in :)