Using custom dependencies and ScriptedImporters triggers "Asset Database is set to Read Only" errors in virtual instances

Unity: Asset - Database

Multiplayer Play Mode

Won't Fix

6.0.X

Registering custom dependencies at any time is currently unsupported for this use-case. Our recommendation is to register custom dependencies in [InitializeOnLoad] or [InitializeOnLoadMethod] . Multiplayer clone instances will do their own domain reload, register the custom dependency locally, and refresh correctly without any errors.

How to reproduce:
1. Download and open the attached project
2. Enable the "Player 2" checkmark in the "Multiplayer Play Mode" window
3. Reimport "Assets/MyScriptedAsset.foo"
4. In the toolbar, select Select "Bug/Update Custom Dependency"

Expected outcome: No errors appear in the "Player 2" window's console
Actual outcome: "Asset Database is set to Read Only, but it has found out-of-date assets. This should not happen!" errors appear in the "Player 2" window's console

Reproduces with: 6000.0.4f1 (Multiplayer Play Mode 1.0.0)
Could not test with: 2021.3, 2022.3 (Project breaks when downgrading, package errors)

Using custom dependencies and ScriptedImporters triggers "Asset Database is set to Read Only" errors in virtual instances

Unity: Asset - Database

Won't Fix

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

Using custom dependencies and ScriptedImporters triggers "Asset Database is set to Read Only" errors in virtual instances

Unity: Asset - Database

Statuses

Won't Fix

Resolution Notes

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?