Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid Exclude in Xcode 13 #70

Closed
adam-redboxmobile opened this issue Sep 3, 2021 · 15 comments
Closed

Invalid Exclude in Xcode 13 #70

adam-redboxmobile opened this issue Sep 3, 2021 · 15 comments

Comments

@adam-redboxmobile
Copy link

Since upgrading to Xcode 13, I'm seeing an Invalid Exclude warning message indicating that the requested file cannot be found.

This applies to:

  • Cryptor.xcodeproj
  • Sources/Info.plist
  • README.md
@willm132
Copy link

willm132 commented Oct 6, 2021

I am still getting this warning

@dannys42
Copy link
Contributor

@willm132 Is this still an issue for you with the latest version?

@babbage
Copy link

babbage commented Nov 2, 2021

I am seeing this warning for files from BlueCryptor, BlueSocket and BlueSSLService, on Xcode 13.1 (13A1030d). The warnings are in all cases "Invalid Exclude... File not found."

For me, these are all dependencies that have been imported by another Swift Package—so it remains possible that it is a configuration issue from a package importing these projects that is the cause of the problem?

The affected files, all in Derived Data folder for SourcePackage checkouts, are:

BlueCryptor
BlueCryptor/Sources/Cryptor/README.md
BlueCryptor/Sources/Cryptor/Sources/Info.plist
BlueCryptor/Sources/Cryptor/Cryptor.xcodeproj

BlueSocket
BlueSocket/Sources/Socket/BlueSocket.xcodeproj
BlueSocket/Sources/Socket/BlueSocket.xcworkspace
BlueSocket/Sources/Socket/README.md
BlueSocket/Sources/Socket/Sources/Info.plist
BlueSocket/Sources/Socket/Sources/Socket.h

BlueSSLService
BlueSSLService/Sources/SSLService/SSLService.xcodeproj
BlueSSLService/Sources/SSLService/README.md
BlueSSLService/Sources/SSLService/Sources/Info.plist

@babbage
Copy link

babbage commented Nov 2, 2021

Ah—I saw elsewhere another project that was encountering this issue and it was associated with an older version of the Package being used. I see for my project, the package pulling in these packages listed above has set the v1 line as the dependency so only Cryptor 1.0.32 is being used. I am guessing that may be part of the issue?

@dannys42
Copy link
Contributor

dannys42 commented Nov 2, 2021

@babbage Yes, that's probably it. Is the parent package a Kitura repo? If so, let me know and I'll take a look at resolving it.

@zntfdr
Copy link

zntfdr commented Nov 2, 2021

If so, let me know and I'll take a look at resolving it.

@dannys42 please take a look at Kitura/Swift-JWT#100, thank you :)

@babbage
Copy link

babbage commented Nov 2, 2021

@babbage Yes, that's probably it. Is the parent package a Kitura repo? If so, let me know and I'll take a look at resolving it.

Turns out these are a dependency of Swift-SMTP, which is indeed a Kitura repo:
https://github.com/Kitura/Swift-SMTP

I checked and I am using the latest version of Swift-SMTP but its dependencies specify:

    dependencies: [
        .package(url: "https://github.com/IBM-Swift/BlueSocket.git", from: "1.0.0"),
        .package(url: "https://github.com/IBM-Swift/BlueSSLService.git", from: "1.0.0"),
        .package(url: "https://github.com/IBM-Swift/BlueCryptor.git", from: "1.0.0"),
        .package(url: "https://github.com/IBM-Swift/LoggerAPI.git", from: "1.7.0"),
        ]

Thanks for taking a look at this @dannys42. Awesome.

@babbage
Copy link

babbage commented Nov 2, 2021

Hmm, searching for dependencies that still specify IBM-Swift/* for these three repos might be a great way to track down other projects that may have the same outdated repos pinned as dependencies, I was thinking. :)

@dannys42
Copy link
Contributor

dannys42 commented Nov 2, 2021

Thanks @babbage. Yes there's a small number of projects that haven't been converted yet largely because they have more complicated testing dependencies (e.g. live servers, additional services, docker containers, etc.) I'll see if I can take care of Swift-SMTP sometime soon though.

@MattTimmons
Copy link

MattTimmons commented Dec 27, 2021

Any update on this? (In reference to Swift-SMTP not building in Xcode 13 for Linux)

@dannys42
Copy link
Contributor

dannys42 commented Dec 28, 2021

@MattTimmons I just pushed a PR for Swift-SMTP to address this. I'm still working on getting the tests to work properly in CI. But if you're able to try this out and run the unit tests successfully, I'll go ahead and tag/release. I found some bugs in the current SMTP auth code, so I'm working through the unit tests and will try to fix the bugs before cutting the release..

@dannys42
Copy link
Contributor

@MattTimmons Ok the PR for Swift-SMTP is now working. Just waiting for code review.

@dannys42
Copy link
Contributor

@MattTimmons Please try release 6.0.0 of Swift-SMTP and let me know if it works for you.

@MattTimmons
Copy link

YES! Works great for me. Using Docker for a Swift Linux build. I do have to have this in my docker file
RUN yum -y install openssl-devel
But everything built great. Thanks!

@dannys42
Copy link
Contributor

dannys42 commented Jan 1, 2022

@adam-redboxmobile and others, can we consider this issue closed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants