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

Swift package manager can't build on Xcode 10.2 anymore #2761

Closed
ChiellieNL opened this Issue Mar 26, 2019 · 8 comments

Comments

Projects
None yet
6 participants
@ChiellieNL
Copy link

ChiellieNL commented Mar 26, 2019

What did you do?

Updated from Xcode 10.1 to Xcode 10.2 (which became available per today)

What did you expect to happen?

I could run swift build and/or swift generate-xcodeproj without errors

What happened instead?

Xcode couldn't build Alamofire due to a manifest error:

https://github.com/Alamofire/Alamofire.git @ 4.8.1: error: manifest parse error(s):
/var/folders/5_/bn8g0cbj2q5_ng_dp9m2lkbr0000gn/T/TemporaryFile.r4j2XW.swift:40:29: error: cannot convert value of type 'Int' to expected element type 'SwiftVersion'
    swiftLanguageVersions: [3, 4]
                            ^

Alamofire Environment

Alamofire version:
4.8.1 as well as 4.8.0
Xcode version:
10.2 (10E125)
Swift version:
Apple Swift version 5.0 (swiftlang-1001.0.69.5 clang-1001.0.46.3)
Target: x86_64-apple-darwin18.2.0
Platform(s) running Alamofire:
iOS/macOS
macOS version running Xcode:
10.14.3

@beatman423

This comment has been minimized.

Copy link

beatman423 commented Mar 26, 2019

same issue happen to me. need help.

@ChiellieNL

This comment has been minimized.

Copy link
Author

ChiellieNL commented Mar 26, 2019

@beatman423 Workaround for now:

Download Xcode 10.1 here: https://developer.apple.com/download/more/
Install and open it, go to preferences and switch Commandline tools back to 10.1
Takes an amount of time and disk usage, but won't block you from working

The guys here are doing a great job btw 👍
It's just Swift that keeps changing their package description continuously without backward compatibility.. sigh

@rex-remind101

This comment has been minimized.

Copy link

rex-remind101 commented Mar 26, 2019

@jshier

This comment has been minimized.

Copy link
Contributor

jshier commented Mar 26, 2019

A hotfix has been merged to our hotfix branch and we'll release it later this week. Target that branch in the mean time. I'll leave this issue open until then.

@ChiellieNL

This comment has been minimized.

Copy link
Author

ChiellieNL commented Mar 26, 2019

Thanks for the quick response Jon!

(although you probably already new) I can confirm
.package(url: "https://github.com/Alamofire/Alamofire.git", .branch("hotfix"))
fixes this issue for me 👍

@Link913

This comment has been minimized.

Copy link

Link913 commented Mar 27, 2019

👍

@jshier

This comment has been minimized.

Copy link
Contributor

jshier commented Mar 27, 2019

4.8.2 has been released with this fix. Thanks!

@ghowen

This comment has been minimized.

Copy link

ghowen commented Apr 1, 2019

@jshier I am still getting this error in a project (LiveUI/Awesome#42) as

    .package(url: "https://github.com/Alamofire/Alamofire.git", from: "4.0.0"),

still pulls 4.8.1. Or do I need to update something? Sorry, no experience with SPM yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.