xcode 11 file fixes

[tanner0101]

Swift packages fetched directly by Xcode 11 are stored in a different location than packages fetched by swift package generate-xcodeproj. Because of this, hacks that were previously used to automatically determine working directory no longer work in Xcode 11.

Luckily, Xcode 11's native SPM integration allows for persistence of project settings. This was a limitation that the original auto-detection hacks were attempting to work around. Because of this, we recommend that all Vapor 3 and 4 users using Xcode 11's native SPM support set a Custom Working Directory in their Run scheme to the desired folder:

This folder is usually the folder that contains your project's Package.swift file.

---

In order for the Custom Working Directory to pass through correctly, a check has been added for a unique string that should only appear when Xcode 11's native SPM integration is being used. This should allow for Vapor 3 projects to continue working normally with swift package generate-xcodeproj.

For Vapor 4, these hacks have been removed entirely, and directory config detection will always expect a Custom Working Directory to be set in the project's Run scheme.

[tanner0101]

Update: It may be possible that Xcode 11 could help us remedy this issue by exposing an environment variable containing the Swift package's root directory.

[tanner0101]

Update to the previous comment: It looks like SPM will not be exposing an environment variable. They gave this response to the feedback assistant request:

We have determined that this issue is not to be fixed/changed.

We considered this but decided not to do it because a package root can change depending on the context. For example, it can be inside a project/workspace.

Thank you for your feedback.

[0xTim]

As an FYI this bug also breaks integrations with the .env support

[tonyarnold]

Oh wow, am I allowed to say that manually setting this scheme configuration is going to be massive PITA when working in Xcode? This essentially means hardcoding an absolute path on a specific machine as the custom working directory, right?