Search Issue Tracker
Third Party Issue
Votes
2
Found in
2019.4
2020.3
2020.3.17f1
2021.1
2021.2
2022.1
Issue ID
1364303
Regression
No
[iOS] Unity includes asmdef excluded .dylib in iOS build
Reproduction steps:
1. Download and open the attached "My Project" project
2. Build and deploy the project to iOS
3. Observe the Console window
Expected result: No errors appear in the Console window
Actual result: "libOVRLipSync.dylib: No such file or directory" error appears in the Console window
Reproducible with: 2019.4.31f1, 2020.3.21f1, 2021.1.26f1, 2021.2.0b16, 2022.1.0a12
Reproduced with: iPhone 12 Pro (iOS 14.2.1), iPhone 6S (iOS 13.3.1)
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
- Tilemap.SetTile() does not change the tiles when called from Update() in the Player
- Custom Shader Material is pink when the project is built for the WebGL platform
- New 3D URP Sample Scenes Project is created with an invalid dependency on com.unity.render-pipelines.universal-config when creating the Sample Project for the first time
- Canvas Scaler causes abnormal scaling of Canvas elements in Play Mode when UI Scale Mode is set to "Constant Physical Size" and any Editor window is moved to a differently scaled monitor and is interacted with
- Touch.rawPosition always returns (0,0) when clicking or dragging anywhere on the screen in the Play Mode
Resolution Note (2022.1.X):
The dylib is included into build by a custom post process script. If you go to Oculus/LipSync/Editor folder, there is OVRLipSyncBuildPostProcessor.cs script which has a code that explicitly adds the .dylib to XCode project.
Note, that in general inclusion of .dylib files into build are not related to asmdef, they are related to plugin settings, though in this case it's a custom post processor playing tricks.