iOS 14 changes to Combine?

Question

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)))

iOS
Combine

1.6k

Posted by

Stammy

Reply

Add a Comment

Answer 1

To answer the question in your subject, Combine changes in beta 1 are as follows:

assign(to:)(aka, "Assign to Published"), a SwiftUI-friendly way of setting up an assign subscriber to republish elements through a Published publisher.
Additional flavors of flatMap(maxPublishers:) and switchToLatest() that account for situations where the inner or outer publishers declare Never as their Failure type.

Posted by

Documentation Engineer

Add a Comment

Answer 2

To answer the question in your subject, Combine changes in beta 1 are as follows:

assign(to:)(aka, "Assign to Published"), a SwiftUI-friendly way of setting up an assign subscriber to republish elements through a Published publisher.
Additional flavors of flatMap(maxPublishers:) and switchToLatest() that account for situations where the inner or outer publishers declare Never as their Failure type.

Posted by

Documentation Engineer

Add a Comment

iOS 14 changes to Combine?

Accepted Reply

Replies