At first I thought it was due to defos as I started getting it after installing defos. But I’m still getting it after removing defos. Work around is to manually delete all the items in the build folder. Which is a pain, because every time I test my game I have to manually delete that folder.
Resolved (It’s defos causing the issue). I had to restart defold after removing defos to fully remove it. Now the issue is fixed.
I guess I’ll report the issue to defos dev.
Did you try to download and build Defos example project from repo : https://github.com/subsoap/defos
Is it working?
I think it’s not Defos issue, but something related to windows/native extensions.
To check it try another native extension or add apmanifest and build.
Yes the example did the same thing.
I’ll check test out it out. What other extensions are like this one though so I can test it out?
Also dies this mean it would be a defold issue if this is an issue with other similar extensions?
I’ve no idea.
Create an appmanifest file and add it in game.project
You are correct. When I add an appmanifest I get that same build error.
Where should I report this as a defold issue? Or to troubleshoot it?
Thank you very much.
All the issues should be reported on GitHub using Editor’s menu option, because then most of the info will be attached to the ticket and you’ll need to fill just a few fields
1 Like
That is so much easier going that way. I never even noticed that menu. I’m glad I asked.
I’m now getting the same issue with the spine extension. I have to manually delete the build folder every time. Which requires me to quit defold so I can delete the files.
But if I build in VS Code…it works fine.
Ok, putting this here so I can remember in the future when/if I hit this issue again.
There was a conflict on my local version of the file and the one in the cloud. So I had to go to my onedrive in the cloud and delete build folder there. Now it works without issue.
The sign that there was an issue is on my local machine the build folder was stuck with this icon showing it wasn’t replicating properly with onedrive.
