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
- ACES Tonemapping causes banding artifacts and negative values in ColorGradingLUT when HDR is enabled and "High Dynamic Range" Grading mode is selected while Android Platform is used
- Android Player freezes when an Audio Source is playing and an incoming call is picked up and then hung up and the Audio Source is started again
- Green success icon is poorly visible in the light Unity theme
- Incorrect input into the Input Field when using Microsoft IME Japanese
- Multiplayer role "ClientAndServer" is displayed without the spaces in the "Play Mode Scenarios" window
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.