#Build fails on Dropbox network drive

1 messages · Page 1 of 1 (latest)

outer pebble
#

after inslaling 3.5.10 exporter unity version 2021.3.23f1 i am getting this error
Build Dev build failed, check the console for errors
UnityEngine.Debug:Log (object)
Needle.Engine.MenuItems/<InternalExportAndBuildTask>d__34:MoveNext () (at Library/PackageCache/[email protected]/Core/Editor/Actions/MenuItems.cs:435)
System.Runtime.CompilerServices.AsyncTaskMethodBuilder1<bool>:SetResult (bool) Needle.Engine.ActionsBuild/<InternalBuildDistTask>d__3:MoveNext () (at Library/PackageCache/[email protected]/Core/Editor/Actions/ActionsBuild.cs:93) System.Runtime.CompilerServices.AsyncTaskMethodBuilder1<bool>:SetResult (bool)
Needle.Engine.Utils.ProcessHelper/<RunCommand>d__4:MoveNext () (at Library/PackageCache/[email protected]/Common/Runtime/Utils/ProcessHelper.cs:275)
UnityEngine.UnitySynchronizationContext:ExecuteTasks ()

I am not able to build dist folder.
I have just created Snadbox(needle) scene, refreshed assets, nothing more.
what can be the problem?

#

Build failed

#

VITE v4.3.8

light vigil
#

Can you click this button and paste the info here?

outer pebble
#

Node.js v20.0.0

light vigil
#

Ah ok it could be because of node 20

#

we havent tested with node 20, we only support node LTS (16 and 18)

outer pebble
#

OK, but with exporter 3.3.0 I have no problem

#

..

#

my old needle project, and all works

light vigil
#

Which vite version was your old project using?

#

And which editor?
If you dont have a specific reason for using Node 20 id still say try to downgrade to 18 LTS

outer pebble
#

I have just installed latest NOde.js some time ago, no specific reason

#

sec, will try 18.16

outer pebble
#

hm not working even with 18.16... will reinstall everything tomorrow

light vigil
#

Ok, if you dont get it to work please try sending a bug via the needle menu item bug reporter

#

Thanks for trying

outer pebble
#

👍

light vigil
#

Hi @outer pebble do you have any news?

outer pebble
#

can this be caused that I am saaving and creating unity project on mapped drive?
I have R: drive and its dropbox shared folder
but one of my last projects was at this drive, and it worked.
I was testing exactly same workflow, once saved at C: and secondly saved on R: and project saved on my C: is working without problems

modern wigeon
#

Build fails on Dropbox network drive

light vigil
#

I think this is different issue where a drive is mapped - not a drive without symlink support

modern wigeon
#

Dropbox / Google Drive are kind of "virtual network drives", I thought they didn't have symlink support either but maybe they do. We should probably exclude both, it's not a good idea to have projects with many files on them - and as far as I'm aware there's no .gitignore or similar for them either

pastel vine
#

I am baffled by the environments people try to use for dev like this 😂 if there are any tutorial makers out there encouraging this I will go tell them off personally

modern wigeon
#

Well, I know firsthand how hard it is to get people to unlearn "put the project where my files sync between machines" and learn "the mystical source control that is git"...

light vigil
#

Some never learn that 🥲