Build failure with BUILD_LIBRARY_FOR_DISTRIBUTION=YES
- Dominant language
- Assembly
- Stars
- 1.7k
- Forks
- 223
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
When will the support for visionOS be provided, for both simulator and physical device?
We have a SDK which consumes swift-cryto as a package dependency (v 2.1.0). We are updating our codebase to support the new OS from Apple. The SDK builds for iOS and MacCatalyst on intel and M1 machines.
Right now when i build from cli with command:
xcodebuild -workspace MySDK.xcworkspace -configuration Debug -sdk xrsimulator build -derivedDataPath ./out -scheme MySDK -destination "generic/platform=visionOS Simulator,OS=latest,name=Apple Vision Pro" "ARCHS=\\x86_64 \\arm64
if fails with the error:
no such module 'CCryptoBoringSSL'
@_implementationOnly import CCryptoBoringSSL
Contributor guide
Research direction
Start by reproducing the reported xcodebuild command for the visionOS Simulator with BUILD_LIBRARY_FOR_DISTRIBUTION=YES and review the @_implementationOnly import CCryptoBoringSSL failure. Compare the package's existing iOS and MacCatalyst build behavior with visionOS simulator and physical-device targets. Done means the package builds for both requested visionOS targets without the missing-module error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- cryptography, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100