Search Unity

Xcode error: no suitable image found (since today's update to Unity 2019.3.0f6 Personal)

Discussion in 'Editor & General Support' started by unity_E9FfAw7RsMp7yg, Feb 11, 2020.

  1. unity_E9FfAw7RsMp7yg

    unity_E9FfAw7RsMp7yg

    Joined:
    Jan 13, 2020
    Posts:
    14
    My environment is MacOS 10.15.3 and Xcode 11.3.1, targeting iOS13.

    I upgraded the Unity Editor in this environment from Unity 2019.2.17f1 Personal to 2019.3.0f6 Personal today.

    My iOS app was building and running fine on a physical iPhone 8, iOS 13.3.1. Ever since the Unity update today, however, I get the following error in Xcode when deploying to this phone, and the app crashes on the phone after briefly displaying a black screen:

     
    aka3eka likes this.
  2. cecarlsen

    cecarlsen

    Joined:
    Jun 30, 2006
    Posts:
    864
    I just ran into the exact same issue. MacOS 10.13.2, Unity 2019.3.1f1, Xcode 10.13.1.

    Did find a work around?
     
    Last edited: Feb 14, 2020
  3. NickMachine

    NickMachine

    Joined:
    May 30, 2017
    Posts:
    1
    I have this same exact problem. Xcode builds the game successfully but when it installs on iphone, the game crashes after the launch screen. We weren't able to find a workaround so we downgraded to 2019.2.x. and that solved our problem. We were successful at building an empty project for iPhone with Unity 2019.3.x but not our game. We kept getting the error mentioned above.
     
    alarm656 likes this.
  4. Johnny-Fuzz

    Johnny-Fuzz

    Joined:
    Sep 1, 2014
    Posts:
    26
    I am having the same thing - has anyone tried Unity 2019.3.0f1?
    Both: 2019.3.0f6 & 2019.3.1f cause issues
     
  5. YasanthaPrabath

    YasanthaPrabath

    Joined:
    Jul 2, 2010
    Posts:
    13
    Last edited: Feb 16, 2020
    fatclarence, alarm656 and Johnny-Fuzz like this.
  6. Johnny-Fuzz

    Johnny-Fuzz

    Joined:
    Sep 1, 2014
    Posts:
    26
  7. AaronStudio

    AaronStudio

    Joined:
    May 8, 2018
    Posts:
    1
    I am experiencing the same issue here.
     
  8. FranFndz

    FranFndz

    Joined:
    Sep 20, 2018
    Posts:
    178
    I tried to update my iOS for 13.4 beta and also Xcode. but i still need to update Mac for 15.xx (I cant update mbp for, company security).

    So, anyone had another idea how to solve this issue? i really need to ge this build
     
  9. Alvarden

    Alvarden

    Joined:
    Feb 22, 2019
    Posts:
    61
    I can confirm that downgrading to 2019.2 or lower solves the problem. Not sure why this is a problem with the lastest version and i hope it gets fixed soon enough.
     
  10. peeka

    peeka

    Joined:
    Dec 3, 2014
    Posts:
    113
    I ran into this with 2019.3.6f1 xcode 11.3.1 help..........
     
  11. Alvarden

    Alvarden

    Joined:
    Feb 22, 2019
    Posts:
    61
    The best you can do is: Export the assets of your project. Create a new project with an older version of Unity. Then import said exported assets to the project and with a bit of luck, you may have imported all your project assets to an older version and you can continue like nothing happened and build the app for IOS. Hope that helped.
     
    unity_XOOZjI06HksBUw likes this.
  12. Alvarden

    Alvarden

    Joined:
    Feb 22, 2019
    Posts:
    61
    Hello again, everyone. I just wanna ask: Does anyone know if that bug has been fixed? Just curious.
     
  13. aka3eka

    aka3eka

    Joined:
    May 10, 2019
    Posts:
    32
  14. Alvarden

    Alvarden

    Joined:
    Feb 22, 2019
    Posts:
    61
    Ok, now that they released Unity 2019 LTS, has anyone tried if the error still persist?
     
  15. FranFndz

    FranFndz

    Joined:
    Sep 20, 2018
    Posts:
    178
    i update unity, xcode and os to catalina.\

    now all work ok
     
  16. alarm656

    alarm656

    Joined:
    Jul 6, 2013
    Posts:
    111
    Unity 2020.1.0f1, Xcode 11.5, Mac OS 10.15.4 still have this error. app is crashing on start
     
  17. triplumi

    triplumi

    Joined:
    Sep 1, 2015
    Posts:
    1
    Got the same error 2020.1.0f1
     
  18. forewar

    forewar

    Joined:
    Sep 9, 2017
    Posts:
    6
    Same here with 2019.4.13f1, XCode 12.0.1, MacOS 10.15.7
     
  19. forewar

    forewar

    Joined:
    Sep 9, 2017
    Posts:
    6
    Updating iOS to 14.2 solved the problem.