Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X
Votes
0
Found in
2020.2.0a17
2020.2.0a18
Issue ID
1265065
Regression
Yes
[iOS] after choosing to append/replace an existing build another window shows up asking if you want to replace it
Reproduction steps:
1. Create a new project and build for iOS
2. Wait for Unity to finish building
3. Build again in the same folder
4. Unity will prompt you to either Append the existing build or completely Replace it
5. Click Append
Expected result: Unity will start appending the build
Actual result: another pop-up window shows up asking if you want to replace the build (read note 2)
Reproducible with: 2020.2.0a17, 2020.2.0a18
Not reproducible with: 2018.4.25f1, 2019.4.5f1, 2020.1.0b16, 2020.2.0a16
Notes:
1. A video of the issue is attached (2020-07-22 14-58-58.mp4)
2. In the background, the build isn't actually replaced but the additional pop-up makes it very confusing
3. I am not sure if any other platform supports existing build appending
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
- Inspector loses focus or Material doesn't update when using GetModifiedMaterial with a Mask component
- Crash on GfxDeviceClient::AllocateBufferInternal when entering Play mode using Graphics.RenderPrimitives and Graphics.DrawProcedural in the scene
- Import TextMesh Pro window opens when the Text Mesh Pro Essentials and Examples are already imported when creating a new TextMesh Pro GameObject in the Hierarchy with TextMesh Pro settings reset
- Video is not rendered when the VideoPlayer GameObject is disabled and re-enabled after playback starts while using Material Override render mode
- Selection outline is not shown when selecting a high intensity HDR Swatch preset in Color Picker
Resolution Note (fix version 2020.2):
Fixed in 2021.1.0a3.823
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0b10.3438
Resolution Note (fix version 2019.4):
Fixed in 2019.4.22f1 (9fdda2fe27ad)
Resolution Note (fix version 2018.4):
Fixed in 2018.4.33f1 (4de2c7344f6c)