Posts

Post not yet marked as solved
6 Replies
13k Views
I compiled my app with Xcode 13 beta and am getting a bunch of runtime warnings like this. I've also noticed someone else on Twitter experiencing the same thing. Any idea what's causing this? Something with my plist file formatting? I don't use Core Data (used to long ago but don't think I have any relics of that in my project anywhere) which was my first thought when seeing NSKeyedUnarchiver. 2021-06-17 00:54:02.295892+0300 RedactedAppName[3659:1216650] [general] *** -[NSKeyedUnarchiver _warnAboutPlistType:missingInAllowedClasses:] allowed unarchiving safe plist type ''NSString' (0x1ef8aebe0) [/System/Library/Frameworks/Foundation.framework]', even though it was not explicitly included in the client allowed classes set: '{(   "'NSDate' (0x1ef8a3e30) [/System/Library/Frameworks/CoreFoundation.framework]",   "'NSDictionary' (0x1ef8a3f98) [/System/Library/Frameworks/CoreFoundation.framework]" )}'. This will be disallowed in the future. 2021-06-17 00:54:02.296016+0300 RedactedAppName[3659:1216650] [general] *** -[NSKeyedUnarchiver _warnAboutPlistType:missingInAllowedClasses:] allowed unarchiving safe plist type ''NSString' (0x1ef8aebe0) [/System/Library/Frameworks/Foundation.framework]', even though it was not explicitly included in the client allowed classes set: '{(   "'NSDate' (0x1ef8a3e30) [/System/Library/Frameworks/CoreFoundation.framework]",   "'NSDictionary' (0x1ef8a3f98) [/System/Library/Frameworks/CoreFoundation.framework]" )}'. This will be disallowed in the future. 2021-06-17 00:54:02.448722+0300 RedactedAppName[3659:1216462] [general] *** -[NSKeyedUnarchiver _warnAboutPlistType:missingInAllowedClasses:] allowed unarchiving safe plist type ''NSString' (0x1ef8aebe0) [/System/Library/Frameworks/Foundation.framework]', even though it was not explicitly included in the client allowed classes set: '{(   "'NSDate' (0x1ef8a3e30) [/System/Library/Frameworks/CoreFoundation.framework]",   "'NSDictionary' (0x1ef8a3f98) [/System/Library/Frameworks/CoreFoundation.framework]" )}'. This will be disallowed in the future.
Posted
by Stammy.
Last updated
.
Post not yet marked as solved
1 Replies
916 Views
I'm in the middle of updating my app to only support iOS 14+ and am moving to the new @main app structure. I'm trying to figure out how to deal with code in my App and Scene Delegate: mainly code related to Core Data and CloudKit persistent container. Stuff like lazy var persistentContainer: NSPersistentCloudKitContainer = {...} and  let context = (UIApplication.shared.delegate as! AppDelegate).persistentContainer.viewContext context.mergePolicy = NSMergeByPropertyObjectTrumpMergePolicy context.automaticallyMergesChangesFromParent = true Where do I put this kind of stuff in the new @main world?
Posted
by Stammy.
Last updated
.
Post marked as solved
1 Replies
1.6k Views
Hey folks, were there any changes to combine in iOS 14? I started running my app in iOS 14 on Xcode beta and began seeing some new errors - does iOS 14 require codingkeys to be specified now even if keys are the same name from imported JSON? Or if there were any changes to how freeform keys work? (the case where the key is a unique value each time, for example a stock ticker like "AAPL" instead of "symbol"). failure(Swift.DecodingError.keyNotFound(CodingKeys(stringValue: "id", intValue: nil), Swift.DecodingError.Context(codingPath: [_JSONKey(stringValue: "example text", intValue: nil), CodingKeys(stringValue: "quote", intValue: nil)], debugDescription: "No value associated with key CodingKeys(stringValue: \"id\", intValue: nil) (\"id\").", underlyingError: nil)))
Posted
by Stammy.
Last updated
.