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

v10.42.0 Carthage.xcframework was built using old swift #8326

Closed
Ogerets opened this issue Aug 1, 2023 · 3 comments · Fixed by #8338
Closed

v10.42.0 Carthage.xcframework was built using old swift #8326

Ogerets opened this issue Aug 1, 2023 · 3 comments · Fixed by #8338

Comments

@Ogerets
Copy link

Ogerets commented Aug 1, 2023

How frequently does the bug occur?

Always

Description

v10.42.0 release contains Carthage.xcframework, which was built with 5.7.2 (swiftlang-5.7.2.135.5 clang-1400.0.29.51).
However the previous v10.41.1 was built using Swift 5.8.1

If I try to build it from sources using latest Swift I get CocoaPodsDynamicExample.xcodeproj cannot be opened because it is missing its project.pbxproj file.

Something is wrong with this release

Stacktrace & log output

No response

Can you reproduce the bug?

Always

Reproduction Steps

  • Create Cartfile with github "realm/realm-swift" "v10.42.0"
  • Run carthage update --use-xcframeworks

Version

v10.42.0

What Atlas Services are you using?

Local Database only

Are you using encryption?

No

Platform OS and version(s)

MacOS Ventura 13.5

Build environment

Xcode version: 14.3.1
Swift: 5.8.1
Dependency manager and version: Carthage 0.39.0

@tgoyne
Copy link
Member

tgoyne commented Aug 2, 2023

Carthage is such a nightmare. It looks like if there's multiple zips on a github release with xcframework in the name it just downloads a pseudorandom one, so sometimes it coincidentally picks the first one and sometimes it doesn't. Because the correct one is the first one, it usually happens to use that one.

A very bad workaround is to repeat rm -rf ~/Library/Caches/org.carthage.CarthageKit && carthage update --use-xcframeworks until it works.

@Ogerets
Copy link
Author

Ogerets commented Aug 2, 2023

@tgoyne Oh, I had the same issue once.
According to Carthage documentation, there is a way to specify binary project specification file with links to proper xcframework archive.
I think this is the proper way to do it, when there's multiple xcframeworks attached to a release.

@Ogerets
Copy link
Author

Ogerets commented Aug 2, 2023

I will look into the problem tomorrow again. Maybe I will come up with the draft PR with fix

Ogerets added a commit to Ogerets/realm-swift that referenced this issue Aug 21, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 17, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants