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
  3. Join us on November 16th, 2023, between 1 pm and 9 pm CET for Ask the Experts Online on Discord and on Unity Discussions.
    Dismiss Notice
  4. Dismiss Notice

Resolved (Case 1412113)[BuildError] OSX 12.3 and Unity 2020.3 - constant build errors

Discussion in 'WebGL' started by matt_cauldron, Mar 20, 2022.

  1. noway2000

    noway2000

    Joined:
    Jul 6, 2022
    Posts:
    5
    Just a heads up, this works perfectly for my students. We are using 2020.3 because most of the tutorials on Unity Learn were created with this version. When our classroom updated to Apple OSX 12.6 Monterey, none of our students could publish to WebGL Unity Play without the "No such file or directory" compiler error.

    STEP 1: Install Python 2 from https://www.python.org/downloads/release/python-2718/ I didn't need to even shut down or restart Unity.

    STEP 2: Add the PreBuildProcessing.cs script to the root Asset folder in your project. I simply created a Unity package and sent it to all of my student's computers. This has to be done once for any new projects.

    I look forward to Unity 2020.3.40f1 so our students don't have to keep doing this. My only other wish is that Gzip would be the default compression as the Brotli compression seems to cause many "WebGL stuck loading at 90%" issues on Unity Play.
     
    sama-van likes this.
  2. owensavag8

    owensavag8

    Joined:
    Dec 16, 2022
    Posts:
    1
    how did you end up getting this to work?
     
  3. sama-van

    sama-van

    Joined:
    Jun 2, 2009
    Posts:
    1,723
    Worked a charm following Step 1 & 2 ! :)
    (Unity 202.3.34f1, Mac OS Ventura 13.2, M1Pro)
     
  4. bottledgalaxy

    bottledgalaxy

    Joined:
    Jul 19, 2019
    Posts:
    84
    Hey, I'm still having this issue on 2020.3.48f1. Probably because I first tried `
    Environment.SetEnvironmentVariable` workaround and not it's still trying to use the one I tried instead of the one coming with this unity version. How can I rollback that setting?

    EDIT: if anyone runs into this, it was just a matter of setting the variable to an empty string. Works now

    Environment.SetEnvironmentVariable("EMSDK_PYTHON", "");