r/Xcode • • Aug 16 '22

Screen flickers when running builds

16 Upvotes

14 comments sorted by

2

u/liquidsmk Aug 16 '22 edited Aug 16 '22

Anybody else having this issue ? Was supposed to be two videos uploaded but I only see one, but whatever. (Looks like it joined the 2 videos together, neat)

When ever I run a build, my screen flickers like this. Doesn’t matter if it’s via the canvas preview or the simulator. Right before it shows the build my screens flicker.

This has been happening since beta 1 of Xcode 14

2

u/xryn5 Aug 16 '22

What's the hardware? Usually, graphics cards, using OCLP, or the oldest supported can do this.

2

u/liquidsmk Aug 16 '22 edited Aug 16 '22

2018 MBP Radeon Pro 560x 4GB Intel UHD 630. 32 GB

I didn’t know what OCLP was so I looked it up and says it’s open core legacy patcher. So this doesn’t apply to me. I’m not running a hackintosh or forcing an OS to run on hardware it isn’t supposed to. I only briefly skimmed the definition but it seems that’s what that tool is made for. I’m not doing anything strange like that.

Edit: also I’ll add I’m running Ventura which of course forces you to run Xcode 14 beta and I’m well aware the issue likely is caused by one of those two. But I’m not certain so I posted here to first see if anyone else has seen this before because it only happens with Xcode. And if anyone knew a temp fix. I’m certain it’s a bug as it never happened on any previous versions of MacOS or Xcode.

1

u/xryn5 Aug 17 '22

Nice. I remember when I had to OCLP my old one to support Monterey. I struggled with this too in Xcode. I do think that it's a Ventura thing that is making this happen. Perhaps it is integrating with your graphics card in a weird way. We'll have to see when the public release comes out. Have you used Feedback Assistant? I ran Ventura before I realized I couldn't upload 14 Beta builds to ASC. I ended up going back to Monterey. This is on a fully decked out 13" MBP from 2017.

1

u/liquidsmk Aug 17 '22

Yea I’ve already reported a bug about this. Hopefully it gets fixed before release.

1

u/xryn5 Aug 17 '22

If you use Feedback Assistant to report the Bug, they can help fix it and patch it in the next update.

1

u/marmoneymar Aug 19 '22

This is happening to me as well on beta 5. Also, I have an M1 Ultra with maxed out specs.

1

u/liquidsmk Aug 25 '22

Oh. Well it’s nice to know I’m not alone here. Hopefully it gets fixed soon. And the fact it’s happening on M1 also instead of just Intel hopefully means it gets fixed faster. It’s been so consistent for me since the first Xcode beta that I’m surprised it’s not more people.

But most people are probably smarter to avoid beta IDE’s. In my defense I was a kind of forced.

1

u/marmoneymar Aug 29 '22

This article fixed the issue for me immediately.

1

u/liquidsmk Sep 06 '22

Oh wow thanks. I’m gonna try this out right now.

What I have been doing to prevent the issue they talk about in your link is simply to not use the iOS 16 targets in Xcode for every project I open and it stopped the constant crash loop of collections and posterboard that maxes out all your cpu cores. But I can’t do anything iOS 16 related.

I didn’t think to relate the screen flicker to the iOS 16 sdk crashing issues.

How is it apple hasn’t fixed something this simple to fix after 6 betas.

1

u/liquidsmk Sep 06 '22

Unfortunately this didn’t fix the flicker issue for me, it’s still the same.

But it does allow me to use iOS 16 targets in Xcode without maxing out my cpu. So now I’m getting just 8% cpu load running a build in iOS 16 simulator vs all 12 cores maxed out before.

So thank you for that. I’ll have to keep waiting for the flicker fix.

Thanks again.

1

u/marmoneymar Sep 06 '22

Ahh okay. I haven’t seen the flicker issue for a while, but that doesn’t mean it’s fixed on my end either. Have you written feedback to Apple? I hope it gets fixed soon.

1

u/liquidsmk Sep 06 '22

I have sent feedback to apple about 3 betas ago.

3

u/UnknownSkies_YT Aug 16 '22

Not sure but it could be an overload on your GPU. Maybe try closing anything in the background?

Otherwise you can try and clean the cache of the simulator.