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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
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.