Search Issue Tracker
Fixed
Fixed in 0.4.3-exp.0
Votes
0
Found in [Package]
0.2.2-exp.0
0.4.3-exp.0
Issue ID
AVPB-25
Regression
No
PolySpatial builds fail due to Xcode interfering with build postprocessors
Reproduction steps:
1. Create a new empty project in Unity 2022.3.5f1
2. Build the Unity project
3. Open the built Xcode project
4. Build the Unity project again (either replace or append)
5. Switch to the open Xcode project while the Unity build is in progress
6. Observe TARGET_OS_XR in the OTHER_CFLAGS build settings
Expected result: TARGET_OS_XR is missing
Actual result: The project is missing TARGET_OS_XR in the OTHER_CFLAGS build settings, causing the Xcode build to fail
Reproduced with: 0.2.2-exp.0 (2022.3.5f1)
Reproducible on: macOS M1 (User Reported)
Not reproducible on: No other environment tested
Note: Not reproduced by CQA
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
- Created asset is placed in a new folder when creating a new folder and instantly creating an asset by clicking somewhere else
- Selecting and deleting transition in Animator does not add to Undo History when animation is previewed in Inspector
- GameObjects remain static when updating constraints of PhysicsJoint with "Enable Sleeping" selected in Havok Physics Configuration
- [iOS] Touch input is not clocked and UI is unresponsive when the application is paused mid-drag without lifting the finger
- [sw-unity-6-1] Scene view renders any light differently when more than one camera exists and neither have the "MainCamera" tag
Resolution Note (fix version 0.4.3-exp.0):
We are not able to reproduce the missing TARGET_OS_XR flag from OTHER_CFLAGS when testing using PolySpatial 0.4.2 package build, 2022.3.11f1 editor, and Xcode 15.1 beta. We are able build the Xcode project successfully.