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
- Create Node Menu is not closing and “NullReferenceException: Object reference not set to an instance of an object” error is thrown when Shader Graph window is closed
- Assert error is thrown when the Editor language is set to one of the experimental ones in an HDRP project
- A BatchDrawCommand is using a pass from the shader “Universal Render Pipeline/Particles/Lit” that is not SRP Batcher compatible
- The Scene does not get rendered in the Player when MSAA is enabled and more than one Camera is used
- Crash on mono_object_get_class when generating Font Atlas of a specific font file
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.