Compilation error in Unity Platforms preview.2-0.2.0

[crocvr]

I updated DOTS Platforms package in Unity 2019.3.0f5 and see compilation errors:

Library\PackageCache\com.unity.platforms@0.2.0-preview.2\Editor\Unity.Platforms\Extensions\FileInfoExtensions.cs(21,42): error CS1061: 'string' does not contain a definition for 'ToForwardSlash' and no accessible extension method 'ToForwardSlash' accepting a first argument of type 'string' could be found (are you missing a using directive or an assembly reference?)

Library\PackageCache\com.unity.platforms@0.2.0-preview.2\Editor\Unity.Platforms\Extensions\FileInfoExtensions.cs(28,35): error CS1061: 'DirectoryInfo' does not contain a definition for 'EnsureExists' and no accessible extension method 'EnsureExists' accepting a first argument of type 'DirectoryInfo' could be found (are you missing a using directive or an assembly reference?)

There is actually more than two errors but they are all as above.

[robertg_unity]

Hi ktitov3d, this look like some left over data in the asset database. I’m afraid this means a “Re-Import All” could fix it. Please try it and let us know if that worked. Thanks!

[frimarichard]

Just to add, I also had these errors after updating. Wiping both the project’s library folder and the global package cache folder did not fix the errors.

[robertg_unity]

Are you still referencing the com.unity.build package? We recently merged the build package into the platforms package, so I wonder if that could cause some conflict.

[brunocoimbra]

@robertg_unity

Are you still referencing the com.unity.build package? We recently merged the build package into the platforms package, so I wonder if that could cause some conflict.

I can confirm that in a clean project it occurs by simply adding the new DOTS Platforms package.

[frimarichard]

@robertg_unity

Are you still referencing the com.unity.build package? We recently merged the build package into the platforms package, so I wonder if that could cause some conflict.

Nope, I’ve never manually referenced it.

[robertg_unity]

Investigating right now, thanks for the report.

[desertGhost]

@robertg_unity

Are you still referencing the com.unity.build package? We recently merged the build package into the platforms package, so I wonder if that could cause some conflict.

I think this is the case. It looks like the Entities 0.5.0-preview.17 lists Build 0.1.0-preview.1 as a dependency.

[robertg_unity]

Thank you everyone for the report.

The package com.unity.entities@0.5.0-preview.17 is currently referencing the package com.unity.build@0.1.0-preview.1 which unfortunately is currently conflicting with the package com.unity.platforms@0.2.0-preview.2.

Until a new version of the entities package is out (which will remove the reference on the build package), please keep the platforms package at version 0.1.8-preview.1.

Thank you for your understanding!

[Richay]

Unfortunately entities 0.5.1 preview 11 still has Unity.Build.Common nested inside, which conflicts with the actual Unity.Build package.

[robertg_unity]

@Richay

Unfortunately entities 0.5.1 preview 11 still has Unity.Build.Common nested inside, which conflicts with the actual Unity.Build package.

Correct, this should be resolved in entities 0.6.0 and above, when its released.

[prajwalshetty_1]

@robertg_unity

Thank you everyone for the report.

The package com.unity.entities@0.5.0-preview.17 is currently referencing the package com.unity.build@0.1.0-preview.1 which unfortunately is currently conflicting with the package com.unity.platforms@0.2.0-preview.2.

Until a new version of the entities package is out (which will remove the reference on the build package), please keep the platforms package at version 0.1.8-preview.1.

Thank you for your understanding!

I can confirm this conflict still happening in 2019.3.0f6 as of feb 9, Waiting for the new entities package, will now downgrade the platforms to 0.1.8-preview.1. Thanks for the update.