Search Issue Tracker
Fixed
Fixed in 6.0.9
Votes
10
Found in [Package]
6.0.8
Issue ID
PBLD-279
Regression
Yes
“The type Unity.ProBuilder UnityEngine.ProBuilder.Shapes.Cube is being serialized by [SerializeReference], but is missing the [Serializable] attribute…” warning is thrown after creating Probuilder GameObject
Reproduction steps:
1. Create a new project
2. Install Probuilder package
3. Create any Probuilder GameObject in Hierarchy (e.g. GameObject > Probuilder > Arch)
4. Observe the Console
Actual result: “The type Unity.ProBuilder UnityEngine.ProBuilder.Shapes.Cube is being serialized by [SerializeReference], but is missing the [Serializable] attribute. To suppress this warning add [Serializable] or use [MakeSerializable].” warning is thrown
Expected result: No errors or warnings are thrown
Reproducible with: 6.0.6 (6000.3.0a5 (f9a1fab5607a)), 6.0.8 (6000.3.0a5 (f9a1fab5607a), 6000.3.0f1, 6000.4.0a5, 6000.5.0a2)
Not reproducible with: 6.0.8 (6000.0.63f1, 6000.2.13f1, 6000.3.0a4)
Reproduced on: macOS Tahoe 26.1 (M4)
Note: FAV is in Editor versions
Comments (4)
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
- [Editor] Multiple "[...] is inaccessible due to its protection level" errors are thrown when opening project with Unity Version Control installed
Shabazza
Dec 27, 2025 00:02
Same here. After update to unity 6.3 LTS from 6.2, I get those warnings for any 3D shapes made with proBuilder 6.0.8.
Seems to be in the auto-generated code.
Baxayaun
Dec 11, 2025 18:32
OMG, you're actually right! I convinced myself that this was an error, but it was, indeed, a warning. Then I checked when this warning was appearing because I thought it appeared when I tried to activate the ProBuilder Edit Mode, which I thought was not visible because of the warning... but no, what happened is that the Edit Mode button moved again to another place in this version! 🤣
So yeah, now I can see that my problem was that I didn't know had to left click the cube icon at the top of the floating Tools Menu to reveal that there are two modes in there: Game Object and ProBuilder. Before, that Edit Mode for ProBuilder was always exposed, but now is hidden!
Well, I appreciate your answer, otherwise I wouldn't have doubted of myself, but I wonder if there are more people out there who thinks that after the update not seeing the Edit Mode button (the yellow one) where it was before is a bug.
Anyways, thank you!
Mat_Anim
Dec 11, 2025 16:07
Hello, while there is a fix in progress, I cannot give a timeline as to when probuilder 6.0.9 will land, as 6.0.8 was released recently.
Just wondering though, is this really a blocking issue? Can't the warning simply be ignored? I'm curious about use cases where it worked in 6000.1, and it's not working in 6000.3 (apart from simply having a warning logged).
Thanks!
Baxayaun
Dec 10, 2025 11:29
I started having this issue after updating Unity from 6000.1 to 6.3 LTS (Windows 10, latest ProBuilder version)
I'm kinda worried because I cannot continue my project level design wise. I need to create new pieces of a modular set and this is preventing me from doing it. I really don't know how long it usually takes for a bug to be solved, but I've seen some that take even months. Is this going to be the case? Otherwise I can just work on those pieces in a different version of the Editor and export them to the one where the issue is active.
Anyway, thanks for your effort! I really love ProBuilder. ❤