Search Issue Tracker
Fixed in 5.4.0
Votes
0
Found in
5.4.0b7
Issue ID
773305
Regression
Yes
Unexpected recursive transfer of MonoBehaviour error on importing package
On importing asset project "Love/Hate" "Unexpected recursive transfer of MonoBehaviour. MonoBehaviour 'Farmer' is being transferred while trying to transfer MonoBehaviour 'Farmer Deed Template Library'" error appears.
To repro:
1. Create a new project.
2. Download/import "Love/Hate" package from AssetStore.
Actual behaviour:
Errors appear:
Unexpected recursive transfer of MonoBehaviour. MonoBehaviour 'Farmer' is being transferred while trying to transfer MonoBehaviour 'Farmer Deed Template Library'
Unexpected MonoBehaviour being transferred. Expecting transfer of MonoBehaviour 'Farmer', but MonoBehaviour being transferred is '(null)'
Binary to YAML conversion: type unsigned int is unsupported
Expected Behaviour: No errors appear.
Regresssion since 5.4.0b5, works fine in 5.4.0b4.
In 5.4.0b4 there is lot of warnings like
Assets/Pixel Crushers/LoveHate/Scripts/Interaction/Deeds/Editor/DeedTemplateLibraryEditor.cs(210,35): warning CS0618: `UnityEditor.EditorGUI.EndDisabledGroup()' is obsolete: `Use DisabledScope instead'
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- GBuffer/Render Deferred Lighting and Render Pass related Errors constantly thrown after switching a Build Profile
- Player settings icons are not retrieved when using "PlayerSettings.GetIcons" method
- Bunch of "TargetParameterCountException" errors thrown in the Editor Console when opening the "Adaptive Probe Volumes" tab in the "Lighting" window
- Non-removable serialized data for a renderer feature still appears even when the renderer feature is deleted
- URP Cascaded Shadows do not have a falloff in Player when the Player is built not in Development Mode
Add comment