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
- Active quality level set on a new Universal 2D project is not the default quality level when creating a new project
- Inspector Open button does nothing when navigating to a different folder with a locked asset
- Pre-generated XML serializers fail to deserialize types that use polymorphism when the Player is built with the IL2CPP scripting backend
- Editor crashes with error "Failed to present D3D11 swapchain due to device reset/removed" and Player freezes when rendering a particle system while using modified URP package on DX11
- Crash on Scripting::LogException when async HTTP callback executes after scripting domain teardown
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.