Xcode suggests version 6.1 but unable to resolve it

[gerchicov-vg]

I was unable to add GzipSwift via Xcode as usually because Xcode suggests version and is unable to use it. I had to change the "from" version manually

[dluffymonkey]

I was unable to add GzipSwift via Xcode as usually because Xcode suggests version and is unable to use it. I had to change the "from" version manually

请问你手动选择的哪个版本呀，我这边手动修改版本为6.0.0也还是不行

[gerchicov-vg]

@dluffymonkey I chose >6.0.0 and it downloaded 6.0.1. It is ok for me but I don't understand why Xcode doesn't do that automatically.
In the same time tag "6.1.0" exists in this repo

[dluffymonkey]

de 不能自动

我也是用的6.0.1，我手动改成6.0.0也会有问题，但是改成6.0.1是成功的

[gerchicov-vg]

I faced another situation with some pod when its new version was already released in its own GitHub repo but it wasn't "released" in cocoapods system. Is it the similar situation?

[joshuagantner]

=6.0.0 swift playground: "Could not resolve package graph. Cannot continue.

expected ',' separator

expected expression in container literal

failedToEvaluateManifest(description: "Build failed because the Mach-O file couldn't be generated.") in https://github.com/1024jp/GzipSwift"

[kaishin]

Same issue here. There seems to be a typo in the 5.10 package file.

[aehlke]

6.0.1 is the latest that works with Xcode 15.4. Either 6.1 requires the beta (haven't tried) or it is just busted.

[gerchicov-vg]

I faced with the same problem even with >=6.0.0 in another project. I tried different options with adding SPM and found out that "=6.0.0" works. Then I just changed back to >=6.0.0