Hello, I tried using this with VContainer .

I had two problems.

1. Uploaded artifact named .unitypackage.zip. (Not a .unitypackage)
2. The created package can open by Unity, but cannot be imported.

Unity's import dialog says:

Nothing to import!
All assets from this package are already in your project.

🤔

• Unity 2019.4.1f1 (macOS)
• workflow yaml
  • https://github.com/hadashiA/VContainer/blob/ku/unitypackage/.github/workflows/release.yaml#L9-L29
• Result
  • https://github.com/hadashiA/VContainer/runs/833573067?check_suite_focus=true

We got this error when trying to use this action to make a .unitypackage for an UdonSharp release.

file:///home/runner/work/_actions/pCYSl5EDgo/create-unitypackage/cfcd3cf0391a5ef1306342794866a9897c32af0b/node_modules/js-yaml/dist/js-yaml.mjs:1273
  return new exception(message, mark);
         ^
YAMLException: incomplete explicit mapping pair; a key node is missed; or followed by a non-tabulated empty line (15:7)

 12 |   validateReferences: 1
 13 |   platformData:
 14 |   - first:
 15 |       : Any
------------^
 16 |     second:
 17 |       enabled: 0

Any idea what we can do to fix this?

Hi @pCYSl5EDgo, I've been using your action for quite a while and it has been very useful! Thank you for this!

I noticed my build started to fail using the recent updates, though:

I've just reverted back to use v1.1.1 and the build succeeded.

I haven't debugged deeply to understand what happened, do you have any clues? Cheers!

Is it possible to still build the package without the project path? I mean when the target folder and git root isn't inside of an unity project. If so, how do I make that happen. I've been trying over 2 hours to get this to work but couldn't do it.

Hey,

My unity project is not the root of the git repo. I can generate a unity package (example: https://github.com/xoorath/xo-unity-spaces/actions/runs/5919493049) but the package itself is not valid.

When inspecting the contents of the package I'm seeing paths like <reponame>/Assets/<inner folder> which is leading me to suspect that the root folder must be the unity project directory in order for this action to work properly.

I've tried changing the working directory of the echo to file steps but the package can not be created: https://github.com/xoorath/xo-unity-spaces/actions/runs/5919565716

The errors produced:

[Error: ENOENT: no such file or directory, open 'Assets/xo-unity-spaces.meta'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: 'Assets/xo-unity-spaces.meta'
}

I'm not sure if this issue is a duplicate of #5.

If I'm right about the issue I would recommend adding a way to change the current working directory or specifying a unity project path.

Hi, I'm trying to package a directory with subdirectories inside and it fails when trying to package these subdirectories.

Error: EISDIR: illegal operation on a directory, copyfile 'Assets/Directory/Subdirectory' -> 'tempFolderkI3Kww/archtemp/9c073fbaccbf4982bbbdb0d1dd95d098/asset' at Object.copyFileSync (fs.js:1907:3) at /home/runner/work/_actions/pCYSl5EDgo/create-unitypackage/master/node_modules/unitypackage/dist/index.js:72:30 at FSReqCallback.oncomplete (fs.js:156:23) { errno: -21, syscall: 'copyfile', code: 'EISDIR', path: 'Assets/Directory/Subdirectory', dest: 'tempFolderkI3Kww/archtemp/9c073fbaccbf4982bbbdb0d1dd95d098/asset'

If I try to package a directory with just files inside it works perfect but there are problems when it has subdirectories.

Many thanks!