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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
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.