Providing an incorrect path should fail the build instead of create a build based on an empty project
See original GitHub issueAfter building my game using this Action, I can’t play it when downloading the artifact. I can build it locally (and it works) but when downloading the generated artifact, it’s unplayable: it just shows a black screen after the “Made with Unity” splashscreen. Also, and maybe related, if I add an icon through Unity player settings, it doesn’t work show in the downloaded artifact. My config file is:
name: Actions
on:
pull_request: {}
push: { branches: [master] }
env:
UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
jobs:
buildAndTestForSomePlatforms:
name: Build for ${{ matrix.targetPlatform }} on version ${{ matrix.unityVersion }}
runs-on: ubuntu-latest
strategy:
fail-fast: false
matrix:
projectPath:
-name-of-my-game
unityVersion:
- 2019.3.3f1 # same as my local Unity version
targetPlatform:
- StandaloneOSX # Build a macOS standalone (Intel 64-bit).
- StandaloneWindows # Build a Windows standalone.
- StandaloneWindows64 # Build a Windows 64-bit standalone.
steps:
- name: Checkout
uses: actions/checkout@v2
with:
lfs: true
- name: Getting cache
uses: actions/cache@v1.1.0
with:
path: ${{ matrix.projectPath }}/Library
key: Library-${{ matrix.projectPath }}-${{ matrix.targetPlatform }}
restore-keys: |
Library-${{ matrix.projectPath }}-
Library-
- name: Build project
uses: webbertakken/unity-builder@v0.15
with:
projectPath: ${{ matrix.projectPath }}
unityVersion: ${{ matrix.unityVersion }}
targetPlatform: ${{ matrix.targetPlatform }}
- name: Uploading artifacts
uses: actions/upload-artifact@v1
with:
name: Build
path: build
I’ve tried using the unity-builder@v0.11
and unity-builder@v0.15
and still nothing. Is it something I’m doing wrong?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:11 (5 by maintainers)
Top Results From Across the Web
Build Failure. Error: 'path' cannot be an empty string ("") or start ...
The problem seems to be with the new lightweight solution loading feature of VS2017. To fix it, first clean up: Close Visual Studio...
Read more >9 QA Error and Warning Messages — The Yocto Project ® 4.1 ...
This check ensures that build system paths (including TMPDIR) do not appear in output files, which not only leaks build system configuration into...
Read more >Troubleshoot broken references - Visual Studio - Microsoft Learn
Another solution is to use the Reference Path item in the project's property pages and modify the folders in the list to point...
Read more >Build Options - Vite
build.emptyOutDir By default, Vite will empty the outDir on build if it is inside project root. It will emit a warning if outDir...
Read more >Makefile projects | CLion Documentation - JetBrains
Go to Settings / Preferences | Build, Execution, Deployment | Build Tools. · Select one of the auto-reload options: Auto-reload settings. Any ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
hey @matthew17754 - an issue I had when I first started was that there were no scenes added to my build settings. Sorry if I’m late to this issue and you’ve resolved it already but it looks like your buildme project doesn’t have any scenes added to the build settings.
https://github.com/matthew17754/unity-ci-test/blob/master/buildme/ProjectSettings/EditorBuildSettings.asset
Hi, sorry for the late answer but in my case I do have scenes on my build (I think right?)
How can I provide you with more information? What do you need?