Search Issue Tracker

Fixed in 2020.2.X

Fixed in 2018.4.X, 2019.4.X, 2020.1.X



Found in


Issue ID




[iOS] Appending an iOS build fails due to missing LaunchImage path error



Steps to reproduce:

1. Create new Unity project
2. Switch target platform to iOS
3. Make an iOS build
4. Make an iOS build again, use the same destination
5. Choose 'Append' when asked to
6. Notice build will fail with the following error message:
DirectoryNotFoundException: Could not find a part of the path '/Users/robertas/Documents/test-append/ios-build/Unity-iPhone/Images.xcassets/LaunchImage.launchimage'.

Reproduced with: 2020.2.0a12
Not reproducible with: 2020.2.0a9

Comments (16)

  1. JulienJnG

    Jan 24, 2021 19:59

    Still happening in 2020.1.17f1 :/

  2. Coryatmarsden

    Jul 08, 2020 20:20

    For people still experiencing this issue, this bug is mentioned as a newly added fix in the 2019.4.3f1 LTS Release Notes.

  3. odysoftware

    Jul 04, 2020 19:54

    Still happening in 2019.4.2f1 - so not fixed in 2019.4?

  4. TheCodingMonkeys

    Jun 30, 2020 19:43

    Well, since this is not going to be fixed for LTS as it seems, I'll leave an (annoying) but working workaround here. add this to any editor directory in your project just touch the offending launch image again.

    using UnityEngine;
    using UnityEditor;
    using UnityEditor.Callbacks;
    using System.Collections;
    using UnityEditor.iOS.Xcode;
    using UnityEditor.Build;
    using UnityEditor.Build.Reporting;
    using System.IO;
    using System.Linq;
    using System.Text.RegularExpressions;

    public class ProjectPostProcessing {

    public static void ChangeXcodePlist(BuildTarget buildTarget, string pathToBuiltProject) {

    if (buildTarget == BuildTarget.iOS) {

    // Temporary Unity 2019.4.0 workaround:
    System.IO.Directory.CreateDirectory(Path.Combine(pathToBuiltProject, "Unity-iPhone/Images.xcassets/LaunchImage.launchimage"));

  5. torikasyu

    Jun 21, 2020 07:37

    Also happening 2019.4.1 LTS

  6. vharutyunyan

    Jun 20, 2020 13:02

    This happens in the latest LTS version therefore it CANNOT HAVE A STATUS OF RESOLVED.

  7. sama-van

    Jun 17, 2020 17:21

    Fixed in 2020.2.0a13

  8. TheCodingMonkeys

    Jun 16, 2020 18:09

    Still Happening in 2019.4.0f with custom storyboard xib. Please reopen or at least reference the still open issue)

  9. Kobald-Klaus

    Jun 15, 2020 15:10

    it´s still happening in 2019.4.0.
    why is this marked as fixed? in what version?

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.