Search Unity

  1. Unity 2019.1 beta is now available.
    Dismiss Notice
  2. The Unity Pro & Visual Studio Professional Bundle gives you the tools you need to develop faster & collaborate more efficiently. Learn more.
    Dismiss Notice
  3. We're looking for insight from anyone who has experience with game testing to help us better Unity. Take our survey here. If chosen to participate you'll be entered into a sweepstake to win an Amazon gift card.
    Dismiss Notice
  4. On February 28th the Feedback website will shut down and be redirected to the Unity forums. See the full post for more information.
    Dismiss Notice
  5. Want to provide direct feedback to the Unity team? Join the Unity Advisory Panel.
    Dismiss Notice
  6. Unity 2018.3 is now released.
    Dismiss Notice
  7. Improve your Unity skills with a certified instructor in a private, interactive classroom. Watch the overview now.
    Dismiss Notice

Vuforia - cloudBuild for iOS fails - windows build OK

Discussion in 'Vuforia' started by dmennenoh, Jan 25, 2019.

  1. dmennenoh

    dmennenoh

    Joined:
    Jul 1, 2015
    Posts:
    256
    I'm using CloudBuild to build for iOS. Using 2018.3 and the latest Vuforia. When I try and build using CB I get all kinds of missing assembly reference errors for Vuforia. Yet I can switch targets and build for Windows just fine.
    I get like 30 of these using CloudBuild:
    Assets/Vuforia/Scripts/DefaultInitializationErrorHandler.cs(18,50): error CS0246: The type or namespace name `VuforiaMonoBehaviour' could not be found. Are you missing an assembly reference?

    and 0 when building locally for Windows.
     
  2. dmennenoh

    dmennenoh

    Joined:
    Jul 1, 2015
    Posts:
    256
    OK - it seems Cloud Build is the problem...
    I can build fine for Android as well, but I can't build for iOS on my machine. Maybe the latest Vuforia is not working on Cloud Build yet? Any idea when this might be fixed? I'm supposed to have this working on iOS already.
     
  3. dmennenoh

    dmennenoh

    Joined:
    Jul 1, 2015
    Posts:
    256
    Sorry, finally saw that CloudBuild was using 2017.2 and not 2018.3. Thought I had set it... works fine now.