Search Issue Tracker
Fixed in 2022.2.0b5
Fixed in 2022.2.X, 2023.1.X, 2023.1.0a5
Votes
1
Found in
2022.2.0b1
2023.1.0a4
Issue ID
UUM-9413
Regression
Yes
[iOS] Archiving an iOS project fails
Steps to reproduce:
- Create a new Unity project
- Switch target to iOS
- Build the project
- Open the generated Xcode project and try to Archive it (Product/Archive)
Expected result: project is successfully archived and prepared for validation/publishing.
Actual result: archiving fails with the following error message:
Bitcode bundle could not be generated because '/Users/robertas/Library/Developer/Xcode/DerivedData/Unity-iPhone-gzsdmyqjzdfnhzgcxkncflagcchs/Build/Intermediates.noindex/ArchiveIntermediates/Unity-iPhone/BuildProductsPath/Release-iphoneos/il2cpp.a(7o14hp7xt8pt.o)' was built without full bitcode. All object files and libraries for bitcode must be generated from Xcode Archive or Install build for architecture arm64
Reproduced with: 2022.2.0b1, 2023.1.0a4
Not reproducible with: 2021.3.6f1
Reproduced using Xcode 13.4 & Xcode 14.0 beta.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment