Search Issue Tracker

Fixed in 2020.1.X

Fixed in 2018.4.X, 2019.4.X

Votes

0

Found in

2018.4

2019.2

2019.2.6f1

2019.3

2020.1

Issue ID

1193341

Regression

No

Package Folders ending in '.Framework' are incorrectly handled and treated as native plugins instead of packages

Asset - Database

-

How to reproduce:
1. Open user-submitted project (PluginImporterPackagesBug)
2. See that the contents of Packages/Framework Package Folder are treated correctly(scripts can be attached to GameObjects, textures displayed by the Inspector)
3. Open the Packages folder outside of Unity
4. Change the name of 'com.unity3d.enginesupport.bug.frameworky' to 'com.unity3d.enginesupport.bug.framework'(names of the folder, inside 'package.json' and 'package.asmdef')
5. Return to Unity
6. See the contents of the package by browsing the package folder in the Project window

Expected result: the package and its contents are handled correctly
Actual result: the package and its contents are handled incorrectly, being identified as a native library

Reproducible with: 2018.4.11f1, 2019.2.10f1, 2019.3.0b8, 2020.1.0a9
Could not test with: 2017.4.33f1(packages not yet implemented)

  1. Resolution Note (fix version 2020.1):

    Fixed in 2020.2.0a16

  2. Resolution Note (fix version 2020.1):

    Fixed in 2020.1.1f1

  3. Resolution Note (fix version 2019.4):

    Fixed in 2019.4.7f1

  4. Resolution Note (fix version 2018.4):

    Fixed in 2018.4.26f1

Log in to vote on this issue

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues