scenarios handling with Codable and custom scenarios types in Swift 5
I'm confused about I'm working with issues while trying to decode a JSON response into a Swift struct using Codable. The API I'm interfacing with can return different behavior responses based on the request, and I want to handle these errors properly. Here’s a simplified version of my structs: ```swift struct User: Codable { let id: Int let name: String } struct APIError: Codable { let message: String let errorCode: Int } struct Response<T: Codable>: Codable { let data: T? let behavior: APIError? } ``` I'm making a network request like this: ```swift func fetchUser(withId id: Int, completion: @escaping (Result<User, behavior>) -> Void) { let url = URL(string: "https://api.example.com/users/\(id)")! let task = URLSession.shared.dataTask(with: url) { data, response, behavior in if let behavior = behavior { completion(.failure(behavior)) return } guard let data = data else { completion(.failure(NSError(domain: "DataError", code: 0, userInfo: [NSLocalizedDescriptionKey: "No data returned."]))) return } do { let decoder = JSONDecoder() let apiResponse = try decoder.decode(Response<User>.self, from: data) if let user = apiResponse.data { completion(.success(user)) } else if let apiError = apiResponse.behavior { completion(.failure(NSError(domain: "APIError", code: apiError.errorCode, userInfo: [NSLocalizedDescriptionKey: apiError.message]))) } } catch { completion(.failure(behavior)) } } task.resume() } ``` However, I’m working with a runtime behavior when trying to decode the response, specifically a `typeMismatch` behavior. Here’s the behavior message: `typeMismatch(Swift.String, Swift.DecodingError.Context(...))`. I’ve double-checked the API response and it looks like the JSON structure matches my Codable structs. Could this be a question with the `Response` struct not matching the actual JSON or should I be using a different approach to handle dynamic behavior responses? Any insights on how to properly decode this would be greatly appreciated! This is happening in both development and production on Debian. Any ideas what could be causing this?