[Bug]: workflowengine embeds different Vue instances, but they might be incompatible

[blizzz]

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

See nextcloud-libraries/nextcloud-vue#6360 for more information

Steps to reproduce

1. see above

Expected behavior

apps hooking into the workflowengine have a working config interface independent of their used Vue version.

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

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Additional info

No response

[blizzz]

cc @juliusknorr

[nickvergessen]

This is also blocking Files automated tagging release nextcloud/files_automatedtagging#1076

[juliusknorr]

I shared a few ideas of what to try with @blizzz but also just patterns that have worked to work around that in the past. The javascript API probably needs some redesign like a callback to just register a render function, but might be more work.

[nickvergessen]

So downgrading to @nextcloud/vue@8.19.0 is the best option for now, and then for 32 we need to make a plan?

[blizzz]

So downgrading to @nextcloud/vue@8.19.0 is the best option for now, and then for 32 we need to make a plan?

I have some things to try out, if they prove fine, there will be some documentation for app devs. Otherwise this is the workaround.

To solve this properly changes on the engine are necessary, and this is 99% backwards incompatible. Being already after feature freeze, this is rather something for 32.

[blizzz]

fixed with #50783 (individual apps may need adjustments)