In 99% of the cases you can safely delete its contents if you want to perform a 100% clean build. This is the internal build folder for the IDE, it usually creates lots of other "garbage" files into the ~/Library/Developer/Xcode/DerivedData directory. If you don't specify this custom work dir, Xcode will try to look for the resources under a random, but uniquely created place somewhere under the DerivedData directory. If you are using Feather CMS, the app will crash without a custom working directory set, because it is required to provide a working environment.
If you run your backend application without explicitly setting a custom working directory, you should see a warning message in Xcode's console. The server is also trying to search for possible dotenv files to configure environmental variables. This working directory usually contains a Resources folder where you can put your Leaf templates and a Public folder which is used by the FileMiddleware. Vapor is using a place called working directory to set the current environment, locate common resources and publicly available files.
Don't worry this is a very common rookie mistake, but what causes this problem exactly? 🤔 When you try to build and run your Vapor application using Xcode you might face the issue that there are some missing files, resources or Leaf templates.
0 kommentar(er)
