Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.3.9
Issue ID
1319918
Regression
Yes
[Collab] Changes are not detected when an error prompt is thrown by DisallowMultipleComponent attribute
How to reproduce:
1. Create a new project with the default 3D template
2. Create an empty Script with the DisallowMultipleComponent attribute
3. Create a few original Prefabs
4. Add the previously created Script on one of the Prefabs
5. Set up Collaborate
6. Publish the initial project
7. In the Project Window, select all of the previously created Prefabs (including the one with the added Script)
8. Through the Component->Scripts tab, add the Script
9. Close the error prompt
10. Inspect the Collaborate Window
Expected result: Changes are listed
Actual result: Changes are not listed
Reproducible with: 1.3.9, 2.1.0-preview.6 (2020.3.1f1, 2021.1.0b12, 2021.2.0a9)
Not reproducible with: 1.2.16 (2018.4.33f1, 2019.4.22f1)
Note:
- Selecting the Prefabs individually in the Project Window, updates them in the Collaborate Window
- Sometimes the issue is not consistent, the regression might not be correct
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Collab is transitioning into maintenance mode as the team works on a replacement service. The team has triaged this issue as Won't Fix as it delays, but does not prevent , prefab changes with this specific attribute from being detected automatically by Collab.