Incorrect color when using matching color profiles

Originator:jay.whitsitt
Number:rdar://20942029 Date Originated:13-May-2015
Status:Closed/7645087 Resolved:Closed
Product:Developer Tools Product Version:
Classification: Reproducible:Yes
 
Summary:
Our designers gave us an Illustrator file with sRGB as the working profile. When I enter the RGB values in the IB color picker and ensure that sRGB is selected, the incorrect color is displayed. I am able to work around this by manually selecting Generic RGB as the profile when entering a color profile, however, this takes 2-3 times as long to perform as the color profile and color picker part of Xcode is buggy and doesn't always keep the values you give it.

To me, if I'm given an sRGB value and enter that with the sRGB profile selected in IB, that should display the correct color

Steps to Reproduce:
To get incorrect color
1. Retrieve #161616/R22G22B22 from the sRGB Illustrator file
2. Select a UIView and open the color picker for its background
3. Ensure sRGB is the color profile selected
4. Enter R22 G22 B22 and click Enter without entering the hex field (to avoid that bug, although repeating this by entering #161616 also produces same result)
5. Run the app in simulator or on a device.
6. R17G17B17 is what is actually displayed on both the simulator and device (which you can see by taking a screenshot then color picking)

Workaround for correct color, although not long-term solution
1. Retrieve #161616/R22G22B22 from the sRGB Illustrator file
2. Select a UIView and open the color picker for its background
3. With the cursor in one of the RGB fields, not the hex field, select Generic RGB as the color profile
4. Enter R22 G22 B22 and click Enter without entering the hex field (to avoid that bug where the profile reverts to sRGB when entering the hex field)
5. Run the app in simulator or on a device.
6. The correct color is shown

Comments

Apple Developer Relations 26-Sep-2016 03:50 PM

Thank you for contacting us.

The original report on this issue, Bug ID 7645087, is closed. The issue was resolved in Xcode 8.

If you still see the issue in a newer release, please file a new bug report.

Please note that you will not be able to directly view the original report in order to keep its information confidential.

If you have further questions about this issue, please update your report again using the Apple Bug Reporter http://bugreport.apple.com.

By jay.whitsitt at Sept. 27, 2016, 12:52 a.m. (reply...)

Apple Developer Relations 26-Sep-2016 03:50 PM

The original report on your issue, Bug ID 7645087, has been closed recently. Please note that you will not be able to directly view the original report in order to keep its information confidential.

If this is still an issue for you, please file a new bug report on the latest releases, e.g. iOS 10, OS X 10.12, Xcode 8.

If you have further questions about this issue, please update your report using the Apple Bug Reporter http://bugreport.apple.com.

By jay.whitsitt at Sept. 27, 2016, 12:52 a.m. (reply...)

Jay Whitsitt 22-Sep-2016 01:45 PM

I see that the duplicate has been closed (7645087). Am I able to know the outcome of that issue?

By jay.whitsitt at Sept. 27, 2016, 12:51 a.m. (reply...)

Marked as duplicate

Apple has marked my bug as a duplicate of 7645087

By jay.whitsitt at May 26, 2015, 6:02 p.m. (reply...)

Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!