question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Providing an incorrect path should fail the build instead of create a build based on an empty project

See original GitHub issue

After 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:closed
  • Created 3 years ago
  • Reactions:1
  • Comments:11 (5 by maintainers)

github_iconTop GitHub Comments

3reactions
darrencperrycommented, May 27, 2020

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

%YAML 1.1
%TAG !u! tag:unity3d.com,2011:
--- !u!1045 &1
EditorBuildSettings:
  m_ObjectHideFlags: 0
  serializedVersion: 2
  m_Scenes:
  - enabled: 0
    path: 
    guid: 00000000000000000000000000000000
  m_configObjects: {}
1reaction
betomalujecommented, Jun 4, 2020

Hi, sorry for the late answer but in my case I do have scenes on my build (I think right?)

%YAML 1.1
%TAG !u! tag:unity3d.com,2011:
--- !u!1045 &1
EditorBuildSettings:
  m_ObjectHideFlags: 0
  serializedVersion: 2
  m_Scenes:
  - enabled: 1
    path: Assets/Scenes/Menu/MainMenu.unity
    guid: cc26a58c1c390e849a32db5af20170e1
  - enabled: 1
    path: Assets/Scenes/LevelAdventure.unity
    guid: 722129650970c4142be7de1d94823afc
  - enabled: 1
    path: Assets/Scenes/LevelViking.unity
    guid: 6d2a2f2e720e2c448a5d62e6a7de3993
  - enabled: 1
    path: Assets/Scenes/AdventureLocal.unity
    guid: ab1935fc1bcb5194ea6b852eb8a24474
  m_configObjects: {}

How can I provide you with more information? What do you need?

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found