ArgumentException: Unknown Type:`Unity.Entities.LinkedEntityGroup`

Unity Engine
, ,
1

Hi,

I recently updated my project to Entities 0.50, and after following the upgrade guide had it working nicely, without any errors or warnings. I’ve since updated the editor to 2020.3.32f1 and that too was fine. I’m only using the packages that Entities gathers as dependencies, com.unity.platforms, Hybrid Renderer and Havok Physics. All good so far…

Last night I updated my MacBook Pro OS, to MacOS 12.3. Since then I can still build to Mac Standalone ok, but when I try to run the standalone executable I get an error in the log which suggests the world isn’t being created properly.

ArgumentException: Unknown Type:`Unity.Entities.LinkedEntityGroup` All ComponentType must be known at compile time. For generic components, each concrete type must be registered with [RegisterGenericComponentType].
  at Unity.Entities.TypeManager.ManagedException (System.Type type) [0x00000] in <00000000000000000000000000000000>:0
  at Unity.Entities.TypeManager.GetTypeIndex[T] () [0x00000] in <00000000000000000000000000000000>:0
  at Unity.Entities.EntityComponentStore.Create (Unity.Entities.EntityComponentStore* entities, System.UInt64 startChunkSequenceNumber, System.Int32 newCapacity) [0x00000] in <00000000000000000000000000000000>:0
  at Unity.Entities.EntityDataAccess.Initialize (Unity.Entities.EntityDataAccess* self, Unity.Entities.World world) [0x00000] in <00000000000000000000000000000000>:0
  at Unity.Entities.WorldUnmanaged.Create (Unity.Entities.World world, Unity.Entities.WorldFlags flags, Unity.Collections.AllocatorManager+AllocatorHandle backingAllocatorHandle) [0x00000] in <00000000000000000000000000000000>:0
  at Unity.Entities.World.Init (Unity.Entities.WorldFlags flags, Unity.Collections.AllocatorManager+AllocatorHandle backingAllocatorHandle) [0x00000] in <00000000000000000000000000000000>:0
  at Unity.Entities.World..ctor (System.String name, Unity.Entities.WorldFlags flags) [0x00000] in <00000000000000000000000000000000>:0
  at Unity.Entities.DefaultWorldInitialization.Initialize (System.String defaultWorldName, System.Boolean editorWorld) [0x00000] in <00000000000000000000000000000000>:0
  at Unity.Entities.AutomaticWorldBootstrap.Initialize () [0x00000] in <00000000000000000000000000000000>:0

I’ve deleted the entire project and re downloaded from source (from before the error), found the package manager cache and cleared it etc. and the error in the standalone build persists. Wondering if this is actually a problem with MacOS or if there is something going on with my Unity install. Or of course there’s a problem in my code that only shows up now?

1 Like
2

You’re not the only one. I’ve had this happen to me with automatic bootstrap, but strangely it only happened when using Release optimization on IL2CPP. Debug IL2CPP and Mono worked fine. I disabled the automatic bootstrap so this error doesn’t happen, but then something else comes crashing down later (full native crash from segfault).
I’m also on 2020.3.32f1 and macOS 12.3.
a bit more info here

1 Like
3

This is overwhelmingly the error you get when TypeManager.Initialize threw an exception. So if you scroll up in the log, you should see the actual problem. Most likely something got stripped that was important.

4

Hi, thanks for responding. It’s literally the only error in the log, ie:

New input system (experimental) initialized
Initialize engine version: 2020.3.32f1 (12f8b0834f07)
[Subsystems] Discovering subsystems at path /Users/nh/Documents/FSProto/Runtime/FSProto.app/Contents/Resources/Data/UnitySubsystems
GfxDevice: creating device client; threaded=1
2022-03-30 08:59:57.415 Anabatica[5665:52999] (null) preferred device: Apple M1 Max (high power)
2022-03-30 08:59:57.415 Anabatica[5665:52999] Metal devices available: 1
2022-03-30 08:59:57.415 Anabatica[5665:52999] 0: Apple M1 Max (high power)
2022-03-30 08:59:57.415 Anabatica[5665:52999] Using device Apple M1 Max (high power)
Initializing Metal device caps: Apple M1 Max
UnloadTime: 0.575083 ms
ArgumentException: Unknown Type:`Unity.Entities.LinkedEntityGroup` All ComponentType must be known at compile time. For generic components, each concrete type must be registered with [RegisterGenericComponentType].
  at Unity.Entities.TypeManager.ManagedException (System.Type type) [0x00000] in <00000000000000000000000000000000>:0
  at Unity.Entities.TypeManager.GetTypeIndex[T] () [0x00000] in <00000000000000000000000000000000>:0
  at Unity.Entities.EntityComponentStore.Create (Unity.Entities.EntityComponentStore* entities, System.UInt64 startChunkSequenceNumber, System.Int32 newCapacity) [0x00000] in <00000000000000000000000000000000>:0
  at Unity.Entities.EntityDataAccess.Initialize (Unity.Entities.EntityDataAccess* self, Unity.Entities.World world) [0x00000] in <00000000000000000000000000000000>:0
  at Unity.Entities.WorldUnmanaged.Create (Unity.Entities.World world, Unity.Entities.WorldFlags flags, Unity.Collections.AllocatorManager+AllocatorHandle backingAllocatorHandle) [0x00000] in <00000000000000000000000000000000>:0
  at Unity.Entities.World.Init (Unity.Entities.WorldFlags flags, Unity.Collections.AllocatorManager+AllocatorHandle backingAllocatorHandle) [0x00000] in <00000000000000000000000000000000>:0
  at Unity.Entities.World..ctor (System.String name, Unity.Entities.WorldFlags flags) [0x00000] in <00000000000000000000000000000000>:0
  at Unity.Entities.DefaultWorldInitialization.Initialize (System.String defaultWorldName, System.Boolean editorWorld) [0x00000] in <00000000000000000000000000000000>:0
  at Unity.Entities.AutomaticWorldBootstrap.Initialize () [0x00000] in <00000000000000000000000000000000>:0

I tried building to IL2CPP Debug configuration as @Anthiese suggested, and it ran correctly, albeit very very slowly. I’ve also tried adding a link.xml, but I’m not sure I’ve got the syntax right?

<linker>

    <assembly fullname="Unity.Entities"/>
    <type fullname="Unity.Entities.*" preserve="all"/>

</linker>
5

This is really odd. We can’t really see how this could happen. How big is your project? Could we see a repro?

6

Hi I’ve sent you a DM with a Dropbox link to a stripped-out project. Thanks!

7

I’ve encontered this problem as well, any feedbacks?

1 Like
8

I’ve encounter this problem as well, and I built my test project which contains com.unity.entities-0.11.2-preview1 pacakge only under Unity 2019.4.36 and Xcode 13.3 (with iOS SDK 15)，these errors appears once start up. It seems irrelevant to code striping cuz i found the generated code of LinkedEntityGroup. I’m looking forward to any progress of this problem, thx.

9

For anyone who finds this issue, After extensive testing we found that it was the Xcode version no longer correctly building, reverting to Xcode version 13.0 resolves this problem.

2 Likes
10

Thanks so much, this fixed it on my side too.