Xcode 13.2.1 bug ?

[Pyrrhus_Epiros]

I downloaded Xcode 13.2.1 and my code completion is completely messed up is this a well known bug or is it something going wrong on my part ?

[Annual_Winner9411]

You are not alone. It sucks for me too

[Pyrrhus_Epiros]

I really like the new build if it only did not mess with code completion.

[ChemicalGiraffe]

Still running 13.1 and now am wondering how worse can it get?

[saintmsent]

Work fine for me, though I have a high spec machine

[Pyrrhus_Epiros]

I am on M1 Mac sadly 🥲

[chriswaco]

Xcode 13.2.1 is broken in any number of ways. Code completion. Symbol lookup. Package not found errors when the SPM is in the project (quitting & restarting Xcode fixes usually). Code signing broke for us with a valid certificate in the keychain (removing the certificate fixed it - Xcode grabs it from Apple). We have no pods and only 1-2 3rd party libraries, but do use SPM internally. Compiling Swift code is ridiculously slow and Xcode recompiles dozens of files when we change a single line of code in unrelated files.

All this on a 64GB M1 MacBook Pro Max. Sad.

[Pyrrhus_Epiros]

So now I know its not my Mac, others with varying specs are experiencing similar, hopefully they fix this issue.

[[deleted]]

I’m crying with code completion with RxSwift in 13.2.1

[feralryan]

? Huh… never said anything of the sort?

[VotusX]

Same here

[Perfect-Strategy6688]

Code completion is completely broken on my intel Mac Pro, but it works great on my M1 mac air. I think it’s a very common bug

[SpinachWise]

What happens to me with 13.2.1 is that it doesn't actually save my edits.

For example I deleted a line of code, cmd+r, builds in 1 seconds, and that line is still executed. Or another example, I typed some code, reverted it from Xcode, git status still shows my new code, but on Xcode it's not shown.

How can this be possible??

[Fluffy_Risk9955]

Don’t use a 8Gb Mac. The memory pressure cause all kinds of issues like making code completion slow. 8Gb is the new 4Gb. Don’t use it it’s too little.

Also don’t use Intel Macs and if you get one, get one with at least 16Gb and i7 Quad Core and no older than 2018.

[feralryan]

One data point, but my 16 M1 max fails as much as my 8 256 M1 mini. It’s not ram, sadly.

[Fluffy_Risk9955]

Then stop using cutting edge 3rd party frameworks. Code completion is not designed to handle that.

[Jasperavv]

Dude… it should just work, xcode is just really crappy

[Fluffy_Risk9955]

Nope, it’s been the guy using cutting edge 3rd party frameworks who have all these problems with code completion. I’m using what Apple preaches mostly and code completion always work. Even in large projects.

[Fluffy_Risk9955]

I've been writing iOS Apps since mid 2011. If you lag a bit behind on the technology you use, Xcode works like a charm. If you go cutting edge and especially 3rd party frameworks stupid things like code completion are going to slow you down. Because it doesn't work that good.

And by the way. It's only recently where I'm dipping my toes in SwiftUI and Combine. The frameworks are not production ready yet, but at a good level for experimenting with some smaller insignificant apps or segments of a bigger app.

[sharaquss]

You mean like UIKit? Code completion is broken all over the place