Experiencing same issue with a custom type. Total joke this is... hours wasted
Mattijah
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
User for
8 years
Post
Replies
Boosts
Views
Activity
I am experiencing similar problem. I increment the app version number let's say from 1.0 to 1.1 and I still have to also increment the build number. If it was 5 I have to change it to 6. This isn't case for iOS. What kind of retardness is this again? They shouldn't at least call it "Build" in Xcode. Also, it wasn't happening to me initially. I had two releases with build number #1 published.
Why do I need to download the latest iOS in order to see older versions? What kind of stupidity is this again?
Getting the same error, using a TextField inside a List. Seems to occur when pressing enter
The recent Xcode releases are absolute ridiculous. Always dealing with some kind of issue.
Same issue here too, although it started happening since Xcode 13.3 and MacOS 12.3. Xcode 13 is the worst release yet. From 1 issue to another. Regret upgrading a big time
Running 13.2. The performance is maybe a little better, but the issue is certainly not 100% resolved and the typing is still behind.
Having the same problem on 13.1 too. Regret updating from a perfectly working Xcode 12.