Search Issue Tracker
Fixed in 2021.3.35f1
Fixed in 2023.2.8f1
Votes
0
Found in
2021.3.27f1
2022.3.3f1
2023.1.1f1
2023.2.0a20
Issue ID
UUM-40479
Regression
Yes
[macOS] Loadable Plugin Directories fail to be exported as .unitypackage
How to reproduce:
1. Open the attached Project "bundleTest"
2. In the Project Window, right-click "Assets/AppleEventIntegration.bundle"
3. In the Context Menu select "Export Package..." and complete the export
4. Observe the Console
Expected result: No errors are thrown and a .unitypackage file is created containing the Plugin
Actual result: No package is created and the following error is thrown in the Console:
"Error while exporting package: No assets to export - only folders. Did you mean to use ExportPackageOptions.Recurse?"
Reproducible with: 2021.3.27f1, 2022.3.3f1, 2023.1.0a25, 2023.1.1f1, 2023.2.0a20
Not reproducible with: 2023.1.0a24
Notes:
- Selecting additional Assets allows the creation of the package, however, importing it back into Unity does not import the Plugin
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
- Context menu item checkmark updates only after reopening twice when using Menu.SetChecked on component context menu items
- Long Property names are not truncated in the Add Property dropdown in the Animation window when the Long Property name does not fit
- [iOS] High CPU load when device keyboard is open
- Selected Animation clip in the Animation window changes when the Domain Reload is triggered
- Animation window scrollbar keeps resetting when the scrollbar width is changed after adding an event
Resolution Note (fix version 2021.3.35f1):
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-37376
Resolution Note (fix version 2023.2.8f1):
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-37376