xcode github

SOLVED. I did log a message before each call of decoder.decodeObject(of: key:) That let me find the issue, and replace: self.aVar = decoder.decodeObject(of: NSArray.self, forKey: someKey) as? someClass by self.aVar = decoder.decodeObject(of: [NSArray.self, NSSet.self, NSNumber.self], forKey: someKey) as? someClass Effectively, someClass has properties that have NSSet properties as well as Int. That was my error, but I still think that Xcode should be able to guess this and provide clearer messages or propose autocompletion. Not yet the case in Xcode 16.4 nor 26.2. I'll file a bug report for enhancement.

We tried your macOS/Xcode but still can't reproduce your error, unfortunately. Okay, well thanks for trying. You'd just need to set language: nil to get the behavior of latin/automatic. But then how would I select the CJK/Automatic or Cyrillic/Automatic options? As far as I can tell, the CreateML framework doesn't distinguish between language and language family, so it's unclear how the Create ML app is able to make this distinction or what the distinction actually means. From the WWDC video I linked to previously, it sounds like there is one model per language family, which would mean there's essentially no difference between choosing Latin/Automatic and Latin/English, or CJK/Automatic and CJK/Japanese. Can you clarify what the difference it? Possible theories include: The language selector menu is just there to reassure users that they made the right choice of family, but it makes no difference under the hood. Picking a specific language changes how the data is tokenized before training. There are

I would (1) delete the entire app folder inside the DerivedData folder inside Users > user > Library > Developer > Xcode and then (2) choose Clean Build Folder under Product in Xcode.

Thanks Albert for replying. Is it an array where you use NSKeyedUnarchiver validateAllowedClass:forKey:? I have a lot of classes with SecureCoding, and I cannot find from the warning in the log where it comes from. What is surprising is that I have commented out all the NSNumber.self in any list of decoder.decodeObject(of:, key:) like if let format = decoder.decodeObject(of: [NSArray.self/*, NSNumber.self*/], forKey: formatKey) as? [[Int]] { And still get the log. *** -[NSKeyedUnarchiver validateAllowedClass:forKey:] allowed unarchiving safe plist type ''NSNumber' (0x204cdbeb8) [/System/Library/Frameworks/Foundation.framework]' for key 'NS.objects', even though it was not explicitly included in the client allowed classes set: '{( 'NSArray' (0x204cd5598) [/System/Library/Frameworks/CoreFoundation.framework] )}'. This will be disallowed in the future. *** -[NSKeyedUnarchiver validateAllowedClass:forKey:] allowed unarchiving safe plist type ''NSNumber' (0x204cdbeb8) [/System/Library/Frameworks/Foundation.framewo

You'd just need to set language: nil to get the behavior of latin/automatic. We tried your macOS/Xcode but still can't reproduce your error, unfortunately.

@marimbasoccer I am unable to reproduce your issue using Xcode 26.2 and iOS 26.2. The report view shows the total activity the first time, the view loads.

Thanks for the help on this! Xcode Version 26.2 (17C52), issue seen on iPhone 17, iOS 26.2 simulator. presentedCount was added to highlight the issue, but main concern is that the alert automatically dismisses the first time it is shown (it's hard to tell in the video, so presentedCount was added to make it more visually apparent). Changing the ViewWithAlert properties to Binding doesn't seem to fix the alert dismissal issue. Sample Xcode project: https://drive.google.com/file/d/10S5_xdl_RZeUVSlqfCrgzIGeBFjLjRyb/view?usp=sharing

Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. I'll check the status next time I do a sweep of forums posts where I've suggested bug reports and post any information about changes I am able to share to this thread. Bug Reporting: How and Why? has tips on creating your bug report.

Thanks for the follow ups. Can’t believe I’m not reproducing so let me take a step back and let’s get this to reproduce. Based on your description, it seems that the inside the is being recreated when the flag changes, causing issues in your SwiftUI view. This behavior might occur because SwiftUI re-evaluates views when state changes, and if the identity of views isn’t stable, it can lead to unnecessary recreations. What Xcode build do you use and what iOS simulator do you use? Can we get this in a focused sample so I can download and run it in different Xcode versions? And also will be good if other SwiftUI engineers take a look because I’m failing to reproduce it, so something I am not doing correctly. If the static text doesn’t recreate, the issue might be related to how handles state updates. Albert Pascual
  Worldwide Developer Relations.

Thanks for the post, this is very interesting, do you have a focused sample I can download and see the code and how it behaves. What version of Xcode are you using and what device iOS version is it running? Have you set on both the cell clipsToBounds = false on both the cell and its contentView? Is it embed the inside a container view? Have you disabled the Liquid Glass in the info.plist to see the difference? I think with a focused simple project will help me understand and will help other developers see what you are seeing and what code is producing this. Albert Pascual
  Worldwide Developer Relations.