Search Issue Tracker
By Design
Votes
0
Found in
2017.2.0b10
Issue ID
947215
Regression
No
AssetDatabase.importPackageCompleted callback doesn't fire if scripts have been recompiled during the import process
Steps to reproduce:
1. Open attached project "947215.zip"
2. Click "Test/ImportPackage" in the Menu Bar
a Unity Package containing one script will be imported
in 'ImportPackage' call a 'Debug.Log("Package Imported")' is added to AssetDatabase.importPackageCompleted callback
3. Wait for the script to get imported and observe the console afterward
Actual result: AssetDatabase.importPackageCompleted callback doesn't fire if scripts have been recompiled during the import process
Reproducible with: 2017.1.1f1, 2017.2.0b11, 2017.3.0a7
Comments (3)
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
- Some Build Profile settings do not remain checked when launching a project without the /Library folder through the command line
- TextMeshPro gradient tags render as literal text when using a font that contains only a part of the ASCII character set
- Small rectangles appearing in the corner of title text in Editor when System Font and Bitmap are selected in preferences
- The shortcut character is typed into the name field when a [Shift + <any alphanumeric key>] shortcut is used to create the asset from "Asset/Create"
- TextMeshPro ligatures broken when Font Style setting is changed from “Lowercase” to “Uppercase”
ynj1988
May 11, 2021 02:19
it is a very embarrassing callback when import package which has script... it makes the complete call back never call ...
BaptisteB
Aug 08, 2018 12:42
No version specified for the fix. And it still don't work on 2018 for me
emptyhead
Oct 16, 2017 15:19
Hello! Which version was this issue fixed in, we don't see it in the changelogs