Search Issue Tracker
Fixed in 2017.2.0f3
Votes
18
Found in
5.5.0b4
Issue ID
831847
Regression
No
[Unet] Error: Assertion failed on expression: 'asset->mainRepresentation.type == TypeOf<GameObject>()' on build Standalone
This happens on all Multiplayer projects upgraded from 5.4. If you remove Library folder - this problem will gone. If you change Player object (for example remove some component) - this problem will gone.
2. How we can reproduce it using the example you attached
1 Open attached project and scene "sc1"
2 Press in menu File->Build and Run, select Standalone as build target and set name for the build and press "Build and Run"-button
Actual result: in the middle of the build process - this error should appear:
"Assertion failed on expression: 'asset->mainRepresentation.type == TypeOf<GameObject>()'
UnityEditor.BuildPlayerWindow:BuildPlayerAndRun()"
3 Find Player object prefab (it is called "Cube") in Project view and remove some component
4 Try to "Build and Run" again - it will be built without errors
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
- "Unexpected exception System.DllNotFoundException" error thrown in the Console window when creating a project with 2D (URP) Template
- [Backport] [XR SDK] [HDRP] XRSettings.gameViewRenderMode does not change Game View Render Mode
- [Backport] [Android][Vulkan] Crash on Samsung Note8 while running gfx tests
- [Backport] Wrong sorting for "GC Alloc" column in Show Related Objects panel of Profiler Window
- [Backport] [iOS] Unfreed allocation errors thrown in Console when executing Build And Run with iOS platform
mayasarii876
Mar 08, 2022 10:39
http://103.56.148.201/
http://103.56.148.201/newmpo
http://103.56.148.201/mpo17
http://103.56.148.201/mpomm
http://103.56.148.201/mpotower
http://103.56.148.201/parisklub
http://103.56.148.201/juraganslot
http://103.56.148.201/mpo500
http://103.56.148.201/mpokick
http://103.56.148.201/mpoyes
http://103.56.148.201/xyzklub
http://103.56.148.201/betmpo
http://103.56.148.201/ogslot88
http://103.56.148.201/hoki777
http://103.56.148.201/mpojuta
http://103.56.148.201/299slot
http://103.56.148.201/mpo188
http://103.56.148.201/mpogacor
http://103.56.148.201/mpo300
http://103.56.148.201/rgo365
http://103.56.148.201/kingdom288
http://103.56.148.201/wigompo
http://103.56.148.201/mpo8899
http://103.56.148.201/mpopelangi
http://103.56.148.201/mpo555
http://103.56.148.201/dutampo
http://103.56.148.201/klik368
http://103.56.148.201/388hero
http://103.56.148.201/19dewa
http://103.56.148.201/mpoxl
http://103.56.148.201/mpoas
http://103.56.148.201/mposun
http://103.56.148.201/qqslot
http://103.56.148.201/mposport
http://103.56.148.201/dewa234
http://103.56.148.201/mesinmpo
CurtisMcGill
Dec 12, 2017 20:54
Deleting Library Folder DOES NOT make you RESTART
1) Exit Unity.
2) Delete or move the directory to a safe location.
3) Run Unity
4) It will REBUILD the Library Folder.
hardcorebadger
May 08, 2017 16:18
Deleting your library doesn't restart your project - it's just the unity cache files - all of "your project" is in the assets folder.
WilmuClass
Feb 16, 2017 05:28
Yes there is. I just fixed the issue by opened the [Camera Rig], Camerea(Head), Camera (Eye), and then pressed on collapse. The error is gone. GL all.
Morning_Fun_Game
Jan 20, 2017 18:00
It came out this issue when I using EditorPrefs.DeleteAll ( ).
Please fix it.
MrLucid72
Nov 08, 2016 17:28
Happens to me on Windows build. Nothing out of the ordinary ... we're a mplayer game, though. Not sure if that makes a diff
bueda
Oct 19, 2016 10:20
The issue occurs for me as well.
I run Unity 5.5.0b2 on Linux, and the issue started appearing after upgrading my project to 5.5.0.b5 and subsequently downgrading back to 5.5.0b2 (as b5 had a couple of annoying bugs).
I removed $project/Library (the Unity Editor cache directory), which was subsequently re-created on reopening the project, and the error is now gone.
It seemed to have caused no issues except for the rather cryptic error messages.
ScionOfDesign
Oct 06, 2016 04:24
I have the same issue. It doesn't seem to affect the build, but it is strange.
FoxCastz
Sep 29, 2016 23:05
Is there a fix to this that doesn't require that I delete my entire library, thus starting my project over?..