Search Issue Tracker

Fixed in 2.2.0

Fixed in 2.2.0-preview.1

Votes

6

Found in [Package]

2.1.0

Issue ID

1140336

Regression

Yes

[2d][Package Manager] All 2d preview packages throw missing namespace errors on installing

Package: 2D Animation

-

2d Animation, 2d IK, 2d Pixel perfect, 2d Spriteshape, 2d psd importer packages throw missing namespace errors on installing even when all the dependencies have been installed.

Steps to reproduce:
1) Create new project.
2) Window > Package Manager.
3) Install 2d Animation.

Actual result: Missing namespace are thrown in console.
Expected result: No errors in console.

Reproducibe in: 2019.2.0a10, 2019.2.0a9, 2019.2.0a8, 2019.2.0a7.
Working fine in: 2019.2.0a6.

Environment: Both Windows and Mac.

Stack trace:
1) Library\PackageCache\com.unity.2d.common@1.1.0-preview.1\Editor\ImagePacker\ImagePackerDebugEditor.cs(28,9): error CS0246: The type or namespace name 'SpriteRect' could not be found (are you missing a using directive or an assembly reference?)

2) Library\PackageCache\com.unity.2d.common@1.1.0-preview.1\Editor\InternalBridge\InternalEditorBridge.cs(33,23): error CS0246: The type or namespace name 'ISpriteEditorDataProvider' could not be found (are you missing a using directive or an assembly reference?)

3)Library\PackageCache\com.unity.2d.common@1.1.0-preview.1\Editor\InternalBridge\InternalEditorBridge.cs(64,50): error CS0246: The type or namespace name 'ISpriteEditor' could not be found (are you missing a using directive or an assembly reference?)

  1. Resolution Note (fix version 2.2.0-preview.1):

    The latest versions of the packages are now Live and available for download in the Package Manager:

    - com.unity.2d.common : 1.2.0-preview.1
    - com.unity.2d.animation : 2.2.0-preview.1
    - com.unity.2d.psdimporter : 1.2.0-preview.1

Comments (3)

  1. The_Phantom16

    May 10, 2019 20:13

    I only got the 'SpriteRect' missing namespace error log in Unity 2019.1 empty project.

  2. TheElumenati

    May 01, 2019 17:55

    I am getting the same bug in 2019.2.0a13

  3. Pozonu

    Apr 23, 2019 10:41

    Still an issue in version 2019.2.0a11

Add comment

Log in to post comment