Search Issue Tracker
Fixed
Fixed in 2022.2.12f1, 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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note (fix version 2023.1.0a9):
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.12f1):
Verified on 2022.2.12f1 on local machine. Bundle plugin is present after xcode build.