Search Issue Tracker
Fixed in 2022.1.X
Votes
7
Found in
2018.4
2019.2.21f1
2019.4
2020.3
2021.1
2021.2
Issue ID
1233645
Regression
No
Xcode linker emits "Ignoring invalid debug info" warnings when archiving a Unity project
How to reproduce:
1. Open the attached "1233645" Unity project
2. Build the "SampleScene" Scene for iOS
3. Open the Xcode project, navigate to Product > Archive and observe the warnings in the Report tab
Expected result: the project is archived fast without a large amount of warnings
Actual result: many "Ignoring invalid debug info" warnings due to libiPhone-lib.a and libil2cpp.a are created
Reproducible with: 2018.4.33f1, 2019.4.25f1, 2020.3.6f1, 2021.1.4f1, 2021.2.0a14
Reproduced on: Xcode Version 11.4 (11E146), 12.3 (12C33)
Not reproducible on: Xcode Version 11.3.1 (11C505)
Notes:
1. The warnings are printed towards the end of the archiving process.
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
- Editor crashes when debugging a for loop
- Crash on UnityPlayer!profiling::ProfilerManager::DisposeProfilerRecorder+0xa when Player gets relaunched and exited after running for a long amount of time
- [Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a9