Tyler-Keith-Thompson / CucumberSwift

A lightweight swift Cucumber implementation
https://tyler-keith-thompson.github.io/CucumberSwift/documentation/cucumberswift/
MIT License
74 stars 19 forks source link

Error Could't load project at: .... #55

Closed uo9qsuf closed 1 year ago

uo9qsuf commented 1 year ago

Tests throw always Couldn't load project at: ... error

/Users/user/Library/Developer/Xcode/DerivedData/CucumberSwiftSample-gkijucsclvpfxlaonviycrdrenry/SourcePackages/checkouts/CucumberSwift/Sources/CucumberSwift/Gherkin/XCode-Specific Couldn't load project at: /Users/user/Library/Developer/Xcode/DerivedData/CucumberSwiftSample-gkijucsclvpfxlaonviycrdrenry/SourcePackages/checkouts/CucumberSwift/Sources/CucumberSwift/Gherkin/XCode-Specific

To Reproduce Steps to reproduce the behavior:

  1. Download the exmaple App
  2. change the package version in the Swift Package manager from 3.1.1 to 3.0.0
  3. run the tests
  4. See error

Expected behavior No error and the tests should run like under version 3.1.1

Additional context Add any other context about the problem here.

Tyler-Keith-Thompson commented 1 year ago

This is because my automated versioning script always bumps the patch version. So there is no tag for 3.0.0, the earliest 3.x version is 3.0.1.

Were you attempting to pin to all 3.x versions when you discovered this? Or is there another use case to support?

I admittedly haven't revisited my versioning scripts since before SPM support

uo9qsuf commented 1 year ago

@Tyler-Keith-Thompson my use case was only to have the newset one :-)

DerFlash commented 1 year ago

Unfortunately we still have this problem.

I switched the SPM dependency to exact 3.3.22, then to up to next major from 3.3.22, also to "branch main". It doesn't matter. I removed derived data and even the ~/Library/Caches/org.swift.swiftpm and restarted Xcode, nothing helped.

Overall everything related to CucumberSwifts' functionality works fine. It's just that Xcode cannot list the folders content:

Bildschirm­foto 2022-12-02 um 12 55 39

And it always shows the said error which confuses our developers. The error isn't even listed in the report navigators build step. Just in Xcodes top bar and the issue navigator. 🤷

mccarron commented 1 year ago

We're seeing the exact same problem as @DerFlash and started seeing it with the newer Xcode 14 builds, maybe was it 14.1?

Tyler-Keith-Thompson commented 1 year ago

Well this is apparently quite serious. Seems like Apple may have broken something out from under me.

I will work on this ASAP, but I have a day job so it may not happen today.

DerFlash commented 1 year ago

Sure thing, hope you had a lovely weekend! Thanks a lot for the quick response and your great work here!

Tyler-Keith-Thompson commented 1 year ago

Thank you for that gentle reminder. My weekend was 100% taken over by said day job. That said, I have a fix out. It required me to clear derived data, but CucumberSwift 3.3.23 does not throw that error (verified in the Sample app)

I am going to leave this issue open for a while just in case anybody else runs into issues that I'm no longer seeing.

mccarron commented 1 year ago

@Tyler-Keith-Thompson that fix worked great, thanks again for that!

DerFlash commented 1 year ago

Works like a charm. Problem's gone! Thanks a lot again!