Description of the bug
In addition to VaadinService, also VaadinSession has a field for DeploymentConfiguration. That is not marked as transient and will be serialized along with the session. This can lead to non-valid data in the configuration if it is modified and a redeploy is done between session store and load.
Expected behavior
DeploymentConfiguration data should always be up-to-date.
Minimal reproducible example
n/a
Versions
- Vaadin / Flow version: latest