-
Notifications
You must be signed in to change notification settings - Fork 3k
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
No longer able to make VisionOS builds for Unity on macos-latest #10219
Comments
HI @StephenHodgson, We are looking in to this issue. |
HI @StephenHodgson , We are facing below error when trying to reproduce your pipeline. Do you have any recommendation, how to workaround it. |
Try using the latest 2022.3 LTS version. 2019.4.40 doesn't support arm64 which is required for the VisionOS platform. In my test in my latest run failure I was using 2021.3.15f1 but didn't expressly install vision os platform. My previous release run was using |
@prasanjitsahoo I updated my dev branch to only test for macos and updated the editor to 2022.3 LTS |
Ok, we will continue to investigate and let you know. |
Hi @StephenHodgson , I am getting Unity license Failure when trying to reproduce the issue. Any recommendation how to reproduce it without license. Attaching failure screenshot |
Sounds like the secrets are not set correctly? You don't need a license, but you do need an account with unity. Set the If already set double check your values. Username should be the email address of your account. I removed the 2FA requirement to make it easier. |
Yes, I have created an UNITY account. Username and password also set to secrets correctly and after removed 2FA, facing same license failure issue |
Still seems like the secret credential itself might still be incorrect.
Here are the results of my latest run if you're unable to repro |
HI @StephenHodgson , Thanks for your quick help on the challenges i faced. I can be able to run the pipelines now without the license and repro the issue. Meanwhile pipelines are getting succeeded now. I could see for your pipelines as well getting succeeded https://github.com/RageAgainstThePixel/unity-build/actions/runs/10057461498/job/27798459949. Attaching my screenshots for the same ![]() |
Yes but 3 hrs on There may still be a misconfiguration issue on the runner image 🤔 I'm still getting these errors on
|
Failed after I merged in release https://github.com/RageAgainstThePixel/unity-build/actions/runs/10065195075/job/27823760428 |
Hi @StephenHodgson Please check now, it is getting passed twice for me today after latest deployment done. |
I can still see from your screen shot that it's taking well over an hour for each step. Which seems like it is still broken. The other builds take less than 20 min and See details in #10219 (comment) |
Yes, We just observed that for arm based machine taking little longer as compared to intel based machine |
Hi @StephenHodgson , |
I updated my tests and GitHub actions to make repro easier: |
Description
Previously I had been able to make automated builds on
macos-latest
with arm64 arch, but recent changes seem to have broken this.I get an error about FMOD trying to initialize but then failing the build after some timeout.
I am able to make automated builds on my self hosted runner with the same tooling as the vanilla GitHub hosted runner.
Platforms affected
Runner images affected
Image version and build link
Is it regression?
yes
Expected behavior
I can perform automated building with Unity Game Engine and Github Actions Runners for Vision OS platform
Actual behavior
Repro steps
See PR RageAgainstThePixel/unity-build#8
UNITY_USERNAME
UNITY_PASSWORD
The text was updated successfully, but these errors were encountered: