Search Issue Tracker
Fixed in 2022.1.X
Duplicate in 2020.3.X
Votes
0
Found in
2019.4
2020.3
2020.3.13f1
2021.1
2021.2
2022.1
Issue ID
1347960
Regression
No
BuildPipeline.BuildPlayer throws "The build cannot be appended" exception when using AcceptExternalModificationsToPlayer option
How to reproduce it:
1. Open the user's attached project "Upgrade.zip"
2. In the menu bar click "shoutr lab" > "Export for Android"
3. Observe the Console window
Expected result: Project is successfully exported
Actual result: Exception "InvalidOperationException: The build cannot be appended." appears
Reproduces on: 2019.4.30f1, 2020.3.19f1, 2021.1.22f1, 2021.2.0b12, 2022.1.0a6
Notes:
- Not reproducible when Exporting project via Build Settings
- Exception appears in line BuildPipeline.BuildPlayer(scenes, pathBuild, BuildTarget.Android, BuildOptions.AcceptExternalModificationsToPlayer);
Comments (2)
-
unity_NIIbl7SGavIp8A
Apr 27, 2022 06:41
Hi, please fix on 2021.3.X .
this issue affects the development iteration cycle. -
EP-Toushirou
Dec 01, 2021 05:46
Hello, when will fix this on 2020.3.X?
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a15