Archive export issues when used as a Swift Package

[ispiropoulos]

We recently started migrating from Cocoapods to SwiftPM for our projects and I faced this issue while exporting an archive:

+ xcodebuild -exportArchive -exportOptionsPlist /var/folders/3v/vf11v3tx64j79b239rzbg_280000gn/T/gym_config20211103-77126-b4sgdz.plist -archivePath '/Users/{SANITIZED_USERNAME}/Library/Developer/Xcode/Archives/2021-11-03/{SANITIZED_PROJECT_NAME} 2021-11-03 17.32.44.xcarchive' -exportPath /var/folders/3v/vf11v3tx64j79b239rzbg_280000gn/T/gym_output20211103-77126-1ub76v
2021-11-03 17:34:05.031 xcodebuild[81855:2683877] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Created bundle at path "/var/folders/3v/vf11v3tx64j79b239rzbg_280000gn/T/{SANITIZED_PROJECT_NAME}_2021-11-03_17-34-05.031.xcdistributionlogs".
2021-11-03 17:34:46.374 xcodebuild[81855:2683877] -[NSNull path]: unrecognized selector sent to instance 0x1fa120340
** INTERNAL ERROR: Uncaught exception **
Uncaught Exception: -[NSNull path]: unrecognized selector sent to instance 0x1fa120340
Stack:
  0   __exceptionPreprocess (in CoreFoundation)
  1   objc_exception_throw (in libobjc.A.dylib)
  2   -[NSObject(NSObject) __retain_OA] (in CoreFoundation)
  3   ___forwarding___ (in CoreFoundation)
  4   _CF_forwarding_prep_0 (in CoreFoundation)
  5   -[IDEDistributionProcessingPipeline process:] (in IDEFoundation)
  6   -[IDEDistributionPackagingStep loadFromExportOptions:error:] (in IDEFoundation)
  7   -[IDEDistributionDriver runWithDestinationPath:error:] (in IDEFoundation)
  8   -[Xcode3CommandLineBuildTool _distributeArchiveAndExit] (in Xcode3Core)
  9   -[Xcode3CommandLineBuildTool run] (in Xcode3Core)
 10   main (in xcodebuild)
 11   start (in dyld)

/Users/{SANITIZED_PROJECT_NAME}/.rvm/gems/ruby-3.0.0/gems/fastlane-2.197.0/gym/lib/assets/wrap_xcodebuild/xcbuild-safe.sh: line 61: 81855 Abort trap: 6           xcodebuild "$@"

When I removed the UIColor-Hex-Swift from Swift Package dependencies the issue was resolved. Please note that using it with Cocoapods does not reproduce the above issue.