Search Issue Tracker

Fixed in 2018.3.X

Fixed in 2018.1.X, 2018.2.X

Votes

5

Found in

2018.1.0a1

2018.1.0b13

Issue ID

1022895

Regression

Yes

[iOS] Xcode compiler errors unknown type name bool in UnityInterface.h

iOS

-

To reproduce:
1. Open attached project "XcodeCompileErrors.zip"
2. Build for iOS
3. Run build with Xcode to iOS device

Expected result: the project is built to iOS device
Actual result: unknown type name bool in UnityInterface.h errors in the Xcode compilers

Reproduced on:
2018.1.0a1 2018.1.0f1 2018.2.0b1

Not reproduced on:
2017.4.1f1

Device:
iPhone SE iOS 9.3
Xcode Version 9.3 (9E145)
MacOS 10.13.4

Comments (19)

  1. infosekr

    Jun 08, 2018 21:16

    Seeing this in 2018.1.3f1 still

  2. syslord2k2

    Jun 08, 2018 12:41

    Automatic solution for cloud build and because it's more comfortable:

    public class PostProcessBuild
    {
    [PostProcessBuild]
    public static void OnPostProcessBuild(BuildTarget target, string path)
    {
    #if UNITY_IPHONE
    string unityInterfacePath = path + "/Classes/Unity/UnityInterface.h";
    if (File.Exists(unityInterfacePath))
    {
    List<string> interfaceLines = File.ReadAllLines(unityInterfacePath).ToList();
    interfaceLines.Insert(0, "#include <stdbool.h>");
    StringBuilder sb = new StringBuilder();
    foreach (string s in interfaceLines)
    {
    sb.Append(s);
    sb.Append("\n");
    }
    File.WriteAllText(unityInterfacePath, sb.ToString());
    }
    else
    {
    Debug.LogError("UnityInterface.h doesn't exist");
    }
    #endif
    }
    }

  3. Chanachon

    Jun 04, 2018 06:01

    I have this problem too, anyone find some solutions?

  4. multimediamarkers

    Jun 01, 2018 19:32

    It is still not working on 2018.1.1f1 ... So why is this issue closed because it is still in!!!!!

  5. GAMEDIA_Justin

    May 28, 2018 08:55

    Still broken in 2018.1.2f1.

    Workaround works fine, but I would love to see this fixed, so our builds in Cloud Build will work again.

  6. mulova

    May 21, 2018 05:36

    Not fixed even in 2018.1.1f1 :(

  7. mc1695

    May 18, 2018 13:45

    I can also confirm this is in 2018.1.0f2 and the suggested workarounds don't work with Unity Cloud Build

  8. Hyperlink_Unity3D

    May 16, 2018 12:45

    Still exist in 2018.1.0f2

    workaround solution is to add #include <stdbool.h> at the top of UNITYINTERFACE.H

  9. dorukeker

    May 10, 2018 13:51

    Also seeing this on 2018.1.0f2

Add comment

Log in to post comment