-
-
Notifications
You must be signed in to change notification settings - Fork 231
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
Restoring Packages With NugetForUnity #276
Comments
Hi @matthew17754 Have you tried |
Or figure out how to call Other examples: |
Hi @matthew17754 , did any of the suggestions work for you? |
I know this thread is closed, but I'm running into a similar problem here and adding The primary error that I'm getting is: Here It's worth mentioning that I am able to build locally. Only my build pipeline has this problem. I am a little suspicious that this isn't a problem with NugetForUnity, but rather a problem with |
I am running into this as well. I don't think the NugetForUnity.NugetHelper.Restore is working either. My running theory is that I have the -ProjectPath set, so it is trying to do the Restore from the Project Path but in reality I need the restore to be called from ProjectPath\Assets. I don't know how to do that ... |
Has anyone had success with using NugetForUnity with GameCI? I've been trying to pass a restore argument to the Unity executable using the
customParameters
field in the yaml file but still end up with missing assembly references during the actions build.We've tried the following arguments with
game-ci/unity-builder@v2
:customParameters: -executeMethod NugetForUnity.NugetHelper.Restore
customParameters: -quit -batchmode -projectPath ${{ matrix.projectPath }} -executeMethod NugetForUnity.NugetHelper.Restore
customParameters: -quit -batchmode -projectPath "${{ matrix.projectPath }}" -executeMethod NugetForUnity.NugetHelper.Restore
The
customParameters
field passes parameters directly to the Unity executable, correct?And if you're wondering, we're just storing the NugetForUnity asset binaries in the repo (yes I know).
The text was updated successfully, but these errors were encountered: