Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.2.X
Votes
0
Found in
2019.4.13f1
2020.1
2020.1.10f1
2020.2
2021.1
Issue ID
1288856
Regression
Yes
BuildOptions.AcceptExternalModificationsToPlayer throws error when building for iOS if the Xcode project does not already exist
How to reproduce:
1. Open the attached '1288856.zip' project
2. Build for iOS via menu bar > BuildMenu > Build
Expected result: Builds succeeds
Actual result: Build fails and 'InvalidOperationException: The build cannot be appended.' error is thrown to the Console
Reproducible with: 2019.4.13f1, 2020.1.10f1, 2020.2.0b8, 2021.1.0a1
Not reproducible with: 2018.4.29f1, 2019.4.12f1, 2020.1.9f1, 2020.2.0b7
Note:
Fix for the issue: change 'buildPlayerOptions.options = BuildOptions.AcceptExternalModificationsToPlayer;' to 'if(BuildPipeline.BuildCanBeAppended(BuildTarget.iOS, "iOSBuild") == CanAppendBuild.Yes) buildPlayerOptions.options |= BuildOptions.AcceptExternalModificationsToPlayer;'
Comments (2)
-
zauberzaubar
Apr 09, 2021 16:46
Still/Again happens on 2020.3.3f
-
LorenzoNuvoletta
Jan 10, 2021 20:10
When is this going to be resolved for 2019.4 LTS?
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
- “Default state” name in Inspector is not truncated when given longer name for “New State” in Animator window
- Upgrading HDRP Project causes the Cloud Layer to warp when using the Global Volume with the Visual Environment enabled
- The Inspector does not shown SkinnedMeshRenderer Bounds when they are overriden by script
- Confusing validation message in Scoped Registries
- Compute shader is dispatched with unsupported workgroup size on multiple browsers when building the project for Web with WebGPU Graphics API
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a7
Resolution Note (fix version 2020.2):
Fixed in 2020.2.3f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.21f1