176

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).

Image 1

Image 2

user3099837
  • 3,931
  • 5
  • 15
  • 13

6 Answers6

193

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

  1. In the simulator, set menu FileGPU SelectionPrefer Integrated GPU to work around this bug.

  2. 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), SettingsAccessibilityDisplay & 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.

zrfrank
  • 2,631
  • 1
  • 12
  • 18
15

Are you using a MacBook Pro? I had the same bug.

I solved in the following ways.

  • Step 1: Unplug all cables, including the charging cable
  • Step 2: Restart the iOS simulator
Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
Kenji Wada
  • 341
  • 1
  • 10
  • 1
    This did work but the issue comes back on starting the Simulator next time when the power cable is connected. – Matoz Dec 15 '20 at 10:30
  • 6
    In light of @zrfrank answer, I guess that unplugging the MacBook makes it switch to its integrated GPU so this can indeed work. It didn't work for me because I had "Prefer Discrete GPU" checked. – Clément Cardonnel Dec 15 '20 at 15:01
  • Works, as long as you don't plug the power back in and restart the simulator again. So I guess unplugging the power cable just make the simulator switch to integrated gpu, and back again to discrete, once the power is back. – d4Rk Dec 16 '20 at 09:37
  • I suggest you try the @zrfrank "Workaround I - Using integrated GPU", it worked just fine on my MBP 2019 (Xcode 12.3, Big Sur 11.0.1) even if I then restart the Simulator again. – Ricardo Barroso Jan 07 '21 at 19:42
6

Best way around it (what I've done), is to download the 14.2 Simulator pack from within Xcode.

  1. Open Xcode->Preferences
  2. Tap Components
  3. Tap the 14.2 Simulator pack and Xcode is going to start installing it.

xcode components It's a workaround till they fix that miserable error.

Mario Zigliotto
  • 8,315
  • 7
  • 52
  • 71
Adam
  • 3,815
  • 29
  • 24
  • 1
    After trying the above mentioned workarounds, this one fixed the problem. For some reason, I previously had a "iPad Pro (12.9-inch) (4th generation) (14.3) in the scheme selector, although just 14.1 and 14.2 simulators were installed. Therefore, this must be changed as well. – Hardy Dec 21 '20 at 07:54
  • However, the SwiftUI previews are not fixed by that, still showing strange things... – Hardy Dec 21 '20 at 07:59
  • 1
    And as every new Xcode there are hundreds of issues to fix before I can continue my work. Thanks Apple!!! BTW none of the mentioned workarounds fixed it... – Sal Dec 24 '20 at 16:57
5

It is Xcode 12.3 bug! you can see that sometimes in the code interface builder too:

same

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.

More description

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!

Mojtaba Hosseini
  • 95,414
  • 31
  • 268
  • 278
2

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.

Dakata
  • 1,227
  • 2
  • 14
  • 33
0

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.

Merid
  • 1
  • 1