Skip to content

mac_catalyst_compilation_errors.md

Latest commit

 

History

History
157 lines (121 loc) · 4.98 KB

mac_catalyst_compilation_errors.md

File metadata and controls

157 lines (121 loc) · 4.98 KB

Mac Catalyst Compilation Errors Analysis

DNSProtocols Test Suite

Executive Summary

The DNSProtocols test suite cannot currently compile for Mac Catalyst due to Swift Package Manager defaulting to macOS targets instead of Mac Catalyst targets. This results in UIKit-dependent dependencies failing to compile.

Root Cause Analysis

Primary Issue: Platform Target Mismatch

  • Expected: Mac Catalyst target (arm64-apple-ios16.0-macabi)
  • Actual: macOS target (arm64-apple-macosx10.13)

Dependency Compilation Failures

The following external dependencies are failing because they import UIKit, which is not available on macOS:

  1. ActiveLabel.swift

    /build/checkouts/ActiveLabel.swift/ActiveLabel/ActiveLabel.swift:10:8: error: no such module 'UIKit'

  2. SkeletonView

    /build/checkouts/SkeletonView/SkeletonViewCore/Sources/API/AnimationBuilder/SkeletonAnimationBuilder.swift:9:8: error: no such module 'UIKit'

  3. SwiftMaskTextfield

    /build/checkouts/swift-mask-textfield/swift-mask-textfield/Sources/Core/SwiftMaskTextfield.swift:25:8: error: no such module 'UIKit'

  4. PhoneNumberKit

    Error: emit-module command failed with exit code 1
(Related to UIKit dependencies)

Swift Package Manager Issues

Platform Configuration

The Package.swift correctly defines Mac Catalyst support:

platforms: [
    .iOS(.v16),
    .tvOS(.v16),
    .macCatalyst(.v16),  // ✅ Correctly defined
    .macOS(.v13),
    .watchOS(.v9),
]

However, Swift Package Manager is not respecting this when building tests and defaults to macOS.

Attempted Solutions That Failed

  1. Swift Build with Target Triple

    swift build --triple arm64-apple-ios16.0-macabi
# Result: Invalid version number errors

  2. Environment Variables

    SDKROOT="iphonesimulator" swift test
# Result: Manifest compilation errors

  3. Direct SwiftC Compilation

    xcrun --sdk iphoneos26.0 swiftc -target arm64-apple-ios16.0-macabi
# Result: Sysroot mismatch warnings

SDK Discovery Issues

Available SDKs identified:

  • iOS 26.0 (iphoneos26.0)
  • iOS Simulator 26.0 (iphonesimulator26.0)
  • macOS 26.0 (macosx26.0)

Missing: No explicit Mac Catalyst SDK found in xcodebuild -showsdks output.

Recommended Solutions

1. Xcode Project Generation (Preferred)

Since Swift Package Manager's command-line tools don't properly handle Mac Catalyst targeting, the best approach is:

  1. Open Package.swift in Xcode
  2. Select Mac Catalyst as the destination
  3. Build/test from within Xcode
  4. Capture compilation errors from Xcode's build log

2. Platform-Specific Dependencies

Consider creating platform-specific dependency configurations:

.target(
    name: "DNSProtocols",
    dependencies: [
        "Alamofire", 
        "DNSCore", 
        .product(name: "UIKit-dependencies", condition: .when(platforms: [.iOS, .macCatalyst]))
    ]
)

3. Conditional Compilation

Use conditional compilation for platform-specific code:

#if canImport(UIKit)
import UIKit
#endif

Test File Analysis

The test files themselves appear to be well-structured and should compile correctly for Mac Catalyst once the platform targeting issue is resolved. Key observations:

  1. Comprehensive Test Coverage: Files like WKRPTCLAccountTests.swift contain extensive protocol validation tests
  2. Mock Implementations: Robust mock worker implementations for testing
  3. Async/Await Support: Modern async testing patterns implemented
  4. Error Handling: Comprehensive error scenario testing

Estimated Error Count

Based on the compilation attempts:

  • External Dependency Errors: ~50-100 errors from UIKit import failures
  • Protocol Resolution Errors: ~100-150 errors from missing dependencies
  • Type Resolution Errors: ~50-75 errors from compilation cascade failures
  • Test-Specific Errors: ~25-50 errors from test file compilation

Total Estimated: ~225-375 errors (consistent with reported 272 errors)

Next Steps

  1. Immediate: Open Package.swift in Xcode and attempt Mac Catalyst build
  2. Short-term: Implement conditional compilation for platform-specific dependencies
  3. Long-term: Consider separating UI-dependent and non-UI protocols into different packages

Compilation Command Recommendations

For future attempts, try these approaches:

  1. Xcode Build

    open Package.swift  # Opens in Xcode
# Then build for Mac Catalyst destination

  2. XcodeBuild with Workspace (if workspace created)

    xcodebuild -scheme DNSProtocols-Package -destination 'platform=macOS,variant=Mac Catalyst'

  3. Swift Build with Explicit Platform (experimental)

    swift build -Xcc -target -Xcc arm64-apple-ios16.0-macabi

The core issue is Swift Package Manager's platform targeting behavior, which requires either Xcode integration or significant Package.swift modifications to resolve properly.