Post

Replies

Boosts

Views

Activity

Xcode 14 false errors are driving me mad
Since Xcode 14 we've been seeing a number of persistent 'false' errors in our project. It's a large project of ~300,000 lines of mostly Swift, some remnants of Objective-C. UI is mostly UIKit but SwiftUI for all new stuff. The files are split between several frameworks with a Workspace. This combo of complexity is apparently causing Xcode to fail to assess the type or location of certain symbols and classes. I have anywhere from 50 to 150 errors which do not prevent me from compiling successfully. It makes refactoring practically impossible since I cannot discern true errors from false ones. Since upgrading to 14.3 the problem has become much, much worse. I have a simple project open now, with one UIViewController, presenting a UIHostingController with a SwiftUI view in it. The SwiftUI struct is showing four errors (preventing compilation this time) for code which does not even exists any more. This after cleaning, deleting Derived Data, and restarting Xcode. How is this possible in a project with literally 4 files in it? Where are these errors being cached? I filed a radar about the false errors. I was asked for logs and data and information. I spent time and effort to gather and supply that, and the ticket has since been completely ignored for months.
1
1
645
May ’23
Waiting for Review times
I uploaded the first build of a new app, waited a week to get In Review. Then got rejected for a missing piece of metadata. I accidentally checked a box indicating I had age-related content which I don't - so I unchecked it, and replied to app review. A message came back the same day asking me to do what I just told them I did. I replied that I had already followed the required steps. Then just nothing for five days. I have no idea if my review was even progressing - with the status "Waiting for Review" and "Unresolved issues". So I had no choice but to cancel the submission and start over. Having been an iOS developer for more than ten years, App Review times have gotten completely unacceptable - to develop an application and have no idea how many weeks it's going to take to crawl through App Review only to be rejected for some trivial checkbox, and get kicked to the back of the queue.
0
0
34
Mar ’26
Xcode 14 false errors are driving me mad
Since Xcode 14 we've been seeing a number of persistent 'false' errors in our project. It's a large project of ~300,000 lines of mostly Swift, some remnants of Objective-C. UI is mostly UIKit but SwiftUI for all new stuff. The files are split between several frameworks with a Workspace. This combo of complexity is apparently causing Xcode to fail to assess the type or location of certain symbols and classes. I have anywhere from 50 to 150 errors which do not prevent me from compiling successfully. It makes refactoring practically impossible since I cannot discern true errors from false ones. Since upgrading to 14.3 the problem has become much, much worse. I have a simple project open now, with one UIViewController, presenting a UIHostingController with a SwiftUI view in it. The SwiftUI struct is showing four errors (preventing compilation this time) for code which does not even exists any more. This after cleaning, deleting Derived Data, and restarting Xcode. How is this possible in a project with literally 4 files in it? Where are these errors being cached? I filed a radar about the false errors. I was asked for logs and data and information. I spent time and effort to gather and supply that, and the ticket has since been completely ignored for months.
Replies
1
Boosts
1
Views
645
Activity
May ’23
Waiting for Review times
I uploaded the first build of a new app, waited a week to get In Review. Then got rejected for a missing piece of metadata. I accidentally checked a box indicating I had age-related content which I don't - so I unchecked it, and replied to app review. A message came back the same day asking me to do what I just told them I did. I replied that I had already followed the required steps. Then just nothing for five days. I have no idea if my review was even progressing - with the status "Waiting for Review" and "Unresolved issues". So I had no choice but to cancel the submission and start over. Having been an iOS developer for more than ten years, App Review times have gotten completely unacceptable - to develop an application and have no idea how many weeks it's going to take to crawl through App Review only to be rejected for some trivial checkbox, and get kicked to the back of the queue.
Replies
0
Boosts
0
Views
34
Activity
Mar ’26