I'm using Carthage to get UIColor-Hex and since the latest Xcode update the repo fails to compile for all architectures.

When I run carthage update I get this error when it reaches the HexColor:

*** Checking out UIColor-Hex-Swift at "2.0"
*** xcodebuild output can be found in /var/folders/06/dgpth9f15tsb1r1_j34528x40000gn/T/carthage-xcodebuild.G2t9PI.log
*** Building scheme "HEXColor-watchOS" in HEXColor.xcodeproj
** CLEAN FAILED **


The following build commands failed:
    Check dependencies
(1 failure)
** BUILD FAILED **


The following build commands failed:
    Check dependencies
(1 failure)
A shell task failed with exit code 65:
** CLEAN FAILED **


The following build commands failed:
    Check dependencies
(1 failure)
** BUILD FAILED **


The following build commands failed:
    Check dependencies
(1 failure)

pod 'UIColor_Hex_Swift', '~> 3.0.2' import UIColor_Hex_Swift

Argument labels '(rgba:)' do not match any available overloads

import HEXColor no such model

Hi, When I try pod 'UIColor_Hex_Swift', '~> 4.0.0' it cause error on pod update. It seems version 4 it's not updated on cocoapods yet. I used pod 'UIColor_Hex_Swift', :git => 'https://github.com/yeahdongcn/UIColor-Hex-Swift.git' and it works

The documentation for getRed(: green: blue: ) explains that older versions of iOS always set the values to a range within 0 and 1, but not any more. When one of these returns outside the expected range, hexString(:) produces invalid hex codes (for example, #54A8FFFFFFDF).

This pull request includes:

1. Xcode Project with shared scheme (New version carthage seems to find no shared scheme for current UIColor-Hex-Swift)
2. XCTestCase instead of Sample
3. init(hex: UInt32) instead of int(rgba: String)

3. is just my suggestion. I wondered if I should make a new repository, but too similar purpose to do so. UInt32 argument leaves us from many exceptions:

• Does it include #?
• Is it hex format? (ex. #FGFFFF)
• Is it not too long? (ex. #FFFFFFFFF)

So, I think UInt32 argument is better than String for UIColor-Hex. Your repository is very famous for UIColor extension for Hex format, so I would like to hear your opinion.

I created initializers for each format.

• init(hex3: UInt16, alpha: CGFloat = 1)
• init(hex4: UInt16)
• init(hex6: UInt32, alpha: CGFloat = 1)
• init(hex8: UInt32)

• Added tests for UIColorInputError.
• Improved functionality for argb2rgba converting.
• Removed .missingHashMarkAsPrefix from UIColorInputError enum.
• Updated readme.

Tried to build the app on Swift 3.0, XCode version 8.2.1 I got the error on linking step.

Undefined symbols for architecture x86_64: "(extension in UIColor_Hex_Swift):__ObjC.UIColor.(init (Swift.String, defaultColor : __ObjC.UIColor) -> __ObjC.UIColor).(default argument 1)"

Hey,

Great git guys.

I followed the installation process and I get an error: Argument labels '(rgba:)' do not match any available overloads')' when i try to add this line in my App Delegate

    UITabBar.appearance().barTintColor = UIColor(rgba: "#12296f")

Do i have to add an import statement? If so what is it? What am i missing?

Thanks a lot

Using Carthage to install UIColor-Hex-Swift and my project's deployment target set to iOS 8.0, I get this error when building:

"Module file's minimum deployment target is ios9.0 v9.0"

Looking at the pod spec, it seems that the minimum version should be 8.0.

I see that the support for SPM has been added, when you will release a new version in order to be able to add the package to SPM?

Now I have the following error:

Can you add support for MacOS You can do it easily with an typealias

I've had to import it to my Mac Project from source rather than cocoapods. Would prefer Cocoapods.

A quick way to support macos Just replace top of UIColorExtension.swift

import UIKit
@objc extension UIColor {

WITH

#if os(iOS)
//---------------------------
//iOS
//---------------------------
import Foundation
import UIKit
typealias AppColor = UIColor

//---------------------------
#elseif os(macOS)
//---------------------------
//macOS
//---------------------------
import Cocoa
typealias AppColor = NSColor

//---------------------------
//#else
// os(tvOS) || os(watchOS)
//---------------------------
#endif


@objc extension AppColor {
    /**
     The shorthand three-digit hexadecimal representation of color.
     #RGB defines to the color #RRGGBB.
     
     - parameter hex3: Three-digit hexadecimal value.
     - parameter alpha: 0.0 - 1.0. The default is 1.0.
     */
    public convenience init(hex3: UInt16, alpha: CGFloat = 1) {
        let divisor = CGFloat(15)
        let red     = CGFloat((hex3 & 0xF00) >> 8) / divisor
        let green   = CGFloat((hex3 & 0x0F0) >> 4) / divisor
        let blue    = CGFloat( hex3 & 0x00F      ) / divisor
        self.init(red: red, green: green, blue: blue, alpha: alpha)
    }
...}

Swift 5 was throwing errors about failable inits and non failable in I had to change init

   public convenience init(_ rgba: String, defaultColor: NSColor = NSColor.clear) {

TO init?

public convenience init?(_ rgba: String, defaultColor: NSColor = NSColor.clear) {

The Cocoapods Specs only has up to version 5.1.7 and not 5.1.9. Is this intended?

[!] CocoaPods could not find compatible versions for pod "UIColor_Hex_Swift":
  In Podfile:
    UIColor_Hex_Swift (~> 5.1.9)

None of your spec sources contain a spec satisfying the dependency: `UIColor_Hex_Swift (~> 5.1.9)`.

https://cocoapods.org/pods/UIColor_Hex_Swift

When I create third part SDK depend on UIColor-Hex-Swift , because of the different name between SwiftPackageManager and Cocoapod, I cant import in the SDK to my app.

when I use the SwiftPackageManage name in my SDK, I cant pod trunk push my SDK to remote, but when I use Pod name in my SDK, I cant use SwiftPackageManage to install my SDK in my App.

Hi,

Thanks for offering a great package.

Swift Package Manager can no longer find UIColor-Hex-Swift after updating to the latest version of Xcode.

Any idea why?

Thanks! Blessings, --Mark

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.