Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice

2017.4 LTS Regression - Building on command-line

Discussion in 'macOS' started by asmaloney, Feb 27, 2020.

  1. asmaloney

    asmaloney

    Joined:
    Jul 25, 2019
    Posts:
    12
    I have a 5.6.x project that I'm working on updating to 2017.4 LTS.

    With my 5.6 project, I have build scripts (bash) that run unity like this:

    "${UNITY_PATH}" -batchmode -quit -logFile build.log -projectPath "${PROJECT_PATH}" -buildOSX64Player Foo.app

    When I updated to 2017 LTS, this is now failing with the following error:

    ---
    DisplayProgressbar: Unity license
    Cancelling DisplayDialog: Failed to activate/update license. Missing or bad username and password. Please try again using valid credentials or contact support@unity3d.com
    This should not be called in batch mode.

    (Filename: /Users/builduser/buildslave/unity/build/Editor/Platform/OSX/EditorUtility.mm Line: 297)
    ---

    How do I fix this so I can build on the command-line again?
     
  2. asmaloney

    asmaloney

    Joined:
    Jul 25, 2019
    Posts:
    12
    So I opened a bug for this regression almost 2 weeks ago. No response there or here.

    Is there anything else I can do to get this regression fixed?
     
    Last edited: Mar 17, 2020
  3. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,518
    Is the Unity license actually activated on the machine? 2017 uses different license from 5.6.
     
  4. asmaloney

    asmaloney

    Joined:
    Jul 25, 2019
    Posts:
    12
    Thank you for the response!

    • I had it working with 5.6.x
    • I used Unity Hub to install the 2017 LTS version
    • I can build and run within the editor
    • It fails when I try to build on the command line

    Given that everything works when I'm not building on the command line, I assume the license is properly activated? How can I tell?
     
  5. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,518
    If you can build within the editor, then the license is activated.

    You aren't running the command line as root are you? Does opening up a new terminal and invoking that command line give you the same behaviour?
     
  6. asmaloney

    asmaloney

    Joined:
    Jul 25, 2019
    Posts:
    12
    I am not running as root.

    I wrote bash scripts to run so I could have automated, reproducible builds. Running them in a new terminal does not change anything.

    I have just verified that it's running using the correct binary ("${UNITY_PATH}" in the initial report):

    /Applications/Unity/Hub/Editor/2017.4.37f1/Unity.app/Contents/MacOS/Unity
     
  7. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,518
    That means the error still reproduces there?
     
  8. asmaloney

    asmaloney

    Joined:
    Jul 25, 2019
    Posts:
    12
    Yes. The resulting log is the same as above.

    If I take just the one build command out of my script (see first post) and run it on the command line, I get the same error and same log.
     
  9. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,518
    I asked QA to take a look at your bug report - hopefully they can reproduce it and we can figure this out.
     
  10. asmaloney

    asmaloney

    Joined:
    Jul 25, 2019
    Posts:
    12
    Great - thank you very much!

    If you need anything at all from my end, or need me to try anything, please let me know.