Search Issue Tracker
Fixed in 2019.4.X
Fixed in 2020.3.X, 2021.1.X, 2021.2.X
Votes
4
Found in
2018.3.14f1
2018.4.0f1
2019.1.0f2
2019.2.0a12
2019.3.0a1
Issue ID
1150985
Regression
Yes
A loop of Prefab AutoSave begins when adding a Parameter to Analytics Event Tracker in Prefab Editing mode
Steps to reproduce:
1. Open the original project "BugReport.zip"
2. Navigate to Project -> Assets and open "TestScene"
3. Select "Image" and enter Prefab editing mode
4. Navigate to Inspector window -> "Analytics Event Tracker" component -> "Send Event" and add a Parameter
-- Notice how Prefab starts to autosave frequently
Expected results: After changing a Prefab it will Autosave 1 time
Actual results: After changing the Prefab a loop of Autosave occurs
Reproducible with: 2018.3.14f1, 2018.4.0f1, 2019.1.0f2, 2019.1.1f1, 2019.2.0a12, 2019.2.0a14, 2019.3.0a1
Not Reproducible with: 2017.4.26f1, 2018.3.13f1, 2019.1.0f1, 2019.2.0a11
Note: In Unity version 2018.3.14f1 there is no need to Enter Prefab edit mode for this bug to occur
Comments (1)
-
unity_0E2620DC1E33ADE0A5D4
Apr 09, 2021 15:33
Unity 2019.4.15.1f
Same bug occurs randomly when trying to save prefab in regular editor
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
Resolution Note (fix version 2019.4):
Update to Analytics Library package version 3.6.11
Resolution Note (fix version 2021.1):
Fixed in 2021.1.20f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.31f1