Today I downloaded the release of Xcode 12.3, and I went running the iOS 14.3 simulators and it seems like there is a graphic glitch that all translucent views are yellow, dock included.
I redownloaded iOS 14.2 and those seem fine. It just seems really odd. I've submitted feedback, but I was curious if anyone else has seen this?
I'm on macOS v10.15.7 (Catalina) and am curious of if it's just Catalina or also macOS v11 (Big Sur).
Xcode 12.4 RC has announced fix.
iOS simulated devices no longer display an incorrect yellow tint in translucent UI elements. Certain GPUs may continue to display the tint with some tvOS simulators. (71203015)
I think it is a bug related to the discrete GPU.
In addition, this bug causes the background of the on-screen keyboard to be almost RGB(0,0,0). Experienced on MBP 2017 with Catalina.
Workaround I - Using integrated GPU
In the simulator, set menu File → GPU Selection → Prefer Integrated GPU to work around this bug.
Restart the simulator.
This was tested on a MacBook Pro with Catalina and Big Sur. As comments suggest that it won't work on iMac.
Workaround II - Reduce transparency
In the simulated device (e.g. iPhone), Settings → Accessibility → Display & Text Size → turn on Reduce Transparency.
Notice that it can only reduce the previous 'solid' yellow to 'fairly light'.
I find this workaround, as the discrete GPU can be used, is more suitable for testing the UI logic than the previous solution.
This was tested on a MacBook Pro with Catalina. Might work on iMac.
Are you using a MacBook Pro? I had the same bug.
I solved in the following ways.
Best way around it (what I've done), is to download the 14.2 Simulator pack from within Xcode.
It's a workaround till they fix that miserable error.
It is Xcode 12.3 bug! you can see that sometimes in the code interface builder too:
It is not critical but If you really care about it, download and use the previous Xcode from here
Nothe that you can't build for iOS 14.3 if you choose to use Xcode 12.2.
Xcode always have unknown issues at the release point. Some of them are critical like this with 54K views! and some are not like this issue with about 5K views in only 13 days. My suggestion is to always have 2 Xcodes at the same time until you are sure about Xcode bugs!
Happened to me as well, while I was charging my MacBook Pro 2016. I closed my Xcode, disconnected my charger from the Macbook and run it again. The problem was fixed.
One thing to point out/confirm: Seems the issue is limited to the simulator. The issue does not persist when sideloading the project to iPhone.
