Search Issue Tracker
Fixed in 2022.2.12f1
Fixed in 2022.2.X, 2023.1.X, 2023.1.0a9
Votes
1
Found in
2022.2.0b3
2023.1.0a1
Issue ID
UUM-11278
Regression
Yes
On macOS, .bundle plugins are broken when using Xcode to generate standalone build
Builds with .bundle plugins in Xcode fail as of 2022.2 when building an exported Xcode project with MacStandalone as the target
Repro:
1) Create a project. Add a .bundle plugin.
2) Build for mac. Make sure the Xcode project generation box is checked.
3) Open project in Xcode and build
Result:
Build fails. The project doesn't have the bundle. Instead it has all of the bundle contents.
Expected:
Succeeds. Only the bundle should be tracked, not its contents.
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
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Duplicated groups and incorrect grouping in UI Builder when using UxmlElementAttribute: libraryPath
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
- Crash on UNITY_FT_Render_Glyph_Internal when Generating Font Atlas in the Font Asset Creator Window
Resolution Note (fix version 2023.1):
Fix an issue with Mac standalone builds where the generated Xcode project did reference .bundle plugins as a single plugin
Resolution Note (fix version 2022.2):
Verified on 2022.2.12f1 on local machine. Bundle plugin is present after xcode build.