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

RealmSwift 10.34.0 install with SPM, compiling error about @Sendable #8104

Closed
ACFancy opened this issue Jan 19, 2023 · 5 comments · Fixed by #8106
Closed

RealmSwift 10.34.0 install with SPM, compiling error about @Sendable #8104

ACFancy opened this issue Jan 19, 2023 · 5 comments · Fixed by #8106

Comments

@ACFancy
Copy link

ACFancy commented Jan 19, 2023

  • RealmSwift 10.34.0 install with SPM, building compiling error:
    • Converting non-sendable function value to ‘@sendable (UInt, UInt) → Bool’ may introduce data races
    • image
    • swift-driver version: 1.62.8 Apple Swift version 5.7 (swiftlang-5.7.0.127.4 clang-1400.0.29.50)
      Target: x86_64-apple-macosx13.0
    • Xcode Version 14.0.1 (14A400)
@ACFancy
Copy link
Author

ACFancy commented Jan 19, 2023

@tgoyne

@DouweBos
Copy link

Getting the same when validating a cocoapod podspec, so this is not a SPM unique issue.

@tgoyne
Copy link
Member

tgoyne commented Jan 20, 2023

I think this is specific to non-macOS Xcode 14.0. I disabled the sendability annotations when building with Xcode 14.0 because too many of the platform SDK types were missing sendable annotations, but in retrospect that was probably because I was testing for macOS and thus still using the macOS 12 SDK.

@ACFancy
Copy link
Author

ACFancy commented Jan 20, 2023

@tgoyne Have some solutions, plan or ideas to solve that compiling error?

@danieljoska
Copy link

Ran into the same issue on MacOS Monterey 12.5 (M2 Apple Silicon) and XCode 14.0.1 when attempting to install and build RealmSwift 10.34.0 with SPM. In my case, the error was fixed by updating XCode to version 14.2 and recompiling.

@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.

4 participants