Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Builds for MacOS broken for (at least) version 2021.2.* #320

Closed
grascm opened this issue Jan 20, 2022 · 9 comments · Fixed by game-ci/docker#158
Closed

Builds for MacOS broken for (at least) version 2021.2.* #320

grascm opened this issue Jan 20, 2022 · 9 comments · Fixed by game-ci/docker#158
Labels
bug in unity This is a bug in unity itself (out of scope) bug Something isn't working

Comments

@grascm
Copy link

grascm commented Jan 20, 2022

Bug description

Build target StandaloneOSX is broken:

2022-01-20T12:42:47.5946800Z *** Tundra build failed (19.30 seconds), 368 items updated, 370 evaluated
2022-01-20T12:42:47.5950193Z Building build/StandaloneOSX/StandaloneOSX.app/Contents/Frameworks/libmono-native.dylib failed with output:
2022-01-20T12:42:47.5951549Z The properties of source file /opt/unity/Editor/Data/PlaybackEngines/MacStandaloneSupport/Variations/macos_x64ARM64_player_nondevelopment_mono/UnityPlayer.app/Contents/Frameworks/libmono-native.dylib could not be retrieved: No such file or directory

How to reproduce

Build any project with targetPlatform set to StandaloneOSX and unity version 2021.2.*

Expected behavior

Build succesfull

Additional details

Required path exists in wrong case:
/opt/unity/Editor/Data/PlaybackEngines/MacStandaloneSupport/Variations/macos_x64arm64_player_nondevelopment_mono/

Official unity forums have bug description and workaround:
https://forum.unity.com/threads/linux-command-line-build-of-macos-has-wrong-mono-path.1200499/

@grascm grascm added the bug Something isn't working label Jan 20, 2022
@webbertakken
Copy link
Member

webbertakken commented Jan 20, 2022

Thank you very much for your bug report. Especially also for linking relevant information!

Ideally we would publish newer images after Unity fixes the bug, but we'll see what we can do if this doesn't get solved by them short term.

@webbertakken webbertakken added the bug in unity This is a bug in unity itself (out of scope) label Jan 20, 2022
@rcoppy
Copy link

rcoppy commented Jan 20, 2022

Hello! Chiming in to say Mac builds are failing for me, too, with an error quite similar to that of @grascm :

Building /github/workspace/build/StandaloneOSX/StandaloneOSX.app/Contents/Frameworks/UnityPlayer.dylib failed with output:
System.ArgumentException: Copy() called on path that doesnt exist: /opt/unity/Editor/Data/PlaybackEngines/MacStandaloneSupport/Variations/macos_x64ARM64_player_nondevelopment_mono/UnityPlayer.app/Contents/Frameworks/UnityPlayer.dylib
   at NiceIO.NPath.CopyWithDeterminedDestination(NPath destination, Func`2 fileFilter)
   at NiceIO.NPath.Copy(NPath dest, Func`2 fileFilter)
   at NiceIO.NPath.Copy(NPath dest)
   at MacOSCodeSignDylibCopy.Run(CSharpActionContext ctx, SignFlags signFlags)

I'll try using the fix linked to in the Unity forum thread.
Thanks!

@webbertakken
Copy link
Member

Thanks! Please let us know your results. Perhaps we can make a specific fix from our side (in this repo) if needed.

@grascm grascm changed the title Builds for MaxOS broken for (at least) version 2021.2.* Builds for MacOS broken for (at least) version 2021.2.* Jan 21, 2022
@ViMaSter
Copy link

After attempting to upgrade a build pipeline from 2020.3.15f2 to 2021.2.8f1, I'm unfortunately running into this issue as well.
As you can see from the full run, Windows and Linux builds still pass and the exact same project using 2020.3.15f2 succeeded building previously.

Any updates on this?

@rcoppy
Copy link

rcoppy commented Jan 27, 2022

It's a huge bummer, yeah; but unfortunately I think it's a blocking issue on the Unity engineering side of things, not game-ci--which means it's going to be a minute before it gets fixed 😢 one thing you can do is open a bug report with Unity themselves through their reporting system; if enough people do that this issue might get higher priority. In the meantime, it might be better to roll back to 2020 LTS. Good luck!!

@webbertakken
Copy link
Member

Did anyone get the suggested fix to work? We might be able to apply it on GameCI side if it works.

Open for PRs

@rcoppy
Copy link

rcoppy commented Jan 28, 2022

Did anyone get the suggested fix to work? We might be able to apply it on GameCI side if it works.

Open for PRs

Unfortunately I don't have a ton of experience with docker and I'm on a rather tight deadline, so I haven't had the time to dive in and figure it out--maybe in a bit! 🙏

@jsm174
Copy link

jsm174 commented Feb 26, 2022

I just ran into this issue as well.

I found a post on the unity forums:
https://forum.unity.com/threads/linux-command-line-build-of-macos-has-wrong-mono-path.1200499/

I tried that solution and made a custom image with the following:

FROM unityci/editor:2021.2.13f1-mac-mono-0
RUN ln -s /opt/unity/Editor/Data/PlaybackEngines/MacStandaloneSupport/Variations/macos_x64arm64_player_nondevelopment_mono /opt/unity/Editor/Data/PlaybackEngines/MacStandaloneSupport/Variations/macos_x64ARM64_player_nondevelopment_mono

@webbertakken, I can create a PR with this fix. Can you point me to where the Docker images are created?

@davidmfinol
Copy link
Member

@jsm174 Here is where the linux images are created: https://github.com/game-ci/docker/blob/main/images/ubuntu/editor/Dockerfile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug in unity This is a bug in unity itself (out of scope) bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants