Verse Backwards Compatibility Errors

The 29.00 release contains support for Verse Persistence. Part of this feature requires changes to persistent weak_maps in Verse to be backwards compatible. More information about this requirement is available in the Verse Persistence documentation. We have identified a bad interaction between backwards compatibility enforcement and asset reflection in UEFN and Creator Portal. We are actively working to fix the issue.

This issue occurs if your Verse code defines modules that are defined using a name that is also used by asset reflection and your Verse code makes use of persistence. Backwards compatibility enforcement will always fail with error code 3532 if the code has been published. Please stand by for updates.

The 29.00 release contains support for Verse Persistence. Part of this feature requires changes to persistent weak_maps in Verse to be backwards compatible. More information about this requirement is available in the Verse Persistence documentation. We have identified a bad interaction between backwards compatibility enforcement and asset reflection in UEFN and Creator Portal. We are actively working to fix the issue.

This issue occurs if your Verse code defines modules that are defined using a name that is also used by asset reflection and your Verse code makes use of persistence. Backwards compatibility enforcement will always fail with error code 3532 if the code has been published. Please stand by for updates.