Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2023.2.0a20
Issue ID
UUM-42951
Regression
No
[MacOS] TypeIndex error appears when building Xcode project
How to reproduce:
1. Download and open the attached project
2. Build a Xcode project for macOS
3. Open and build the Xcode project
4. Observe the Xcode console
Expected outcome: No errors appear
Actual outcome: "TypeIndex typeIndex = MetadataOffset<TypeIndex>(s_GlobalMetadata, s_GlobalMetadataHeader->unresolvedIndirectCallParameterTypesOffset, range->start + j);" error appears
Reproducible with: 2023.2.0a20
Could not test with: 2020.3, 2021.3, 2022.3, 2023.1 (Project breaks/errors when downgrading)
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
- Mesh Renderer Component uses default editor when applying custom editor
- Editing a Template is not disabled when the Template signature is in progress but if the Template is edited the Template signature fails
- Changing Signing organization on a Template still shows the same organization in the Hub
- [Android] Navigation bar does not go away when tapping on the screen to close the keyboard
- "InvalidOperationException" is thrown when clicking "Ctrl+Z" after opening Gradient Editor
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (2023.2.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.