macOS 13.1 - SwiftUI App Freezes When Loading Large JSON Files from URL
I'm deploying to production and I'm working on a project and hit a roadblock... I'm developing a SwiftUI app on macOS 13.1 and facing an issue where the app freezes when attempting to load a large JSON file from a URL. The JSON file is about 5MB in size, and when I try to fetch it using `URLSession`, the main thread locks up for several seconds, making the UI unresponsive. Here's the code I've been using: ```swift import SwiftUI struct ContentView: View { @State private var data: [MyModel] = [] @State private var isLoading = false var body: some View { VStack { if isLoading { ProgressView("Loading...") } else { List(data) { item in Text(item.title) } } } .onAppear { loadData() } } private func loadData() { isLoading = true let url = URL(string: "https://example.com/largefile.json")! URLSession.shared.dataTask(with: url) { (data, response, error) in guard let data = data, error == nil else { print("Error fetching data: \(error!)"); return } do { let decoder = JSONDecoder() self.data = try decoder.decode([MyModel].self, from: data) DispatchQueue.main.async { self.isLoading = false } } catch { print("Error decoding JSON: \(error)") DispatchQueue.main.async { self.isLoading = false } } }.resume() } } struct MyModel: Codable, Identifiable { let id: Int let title: String } ``` I've tried moving the JSON decoding to a background thread using `DispatchQueue.global()`, but even that doesn't seem to help with the UI freezing. The JSON decoding is done correctly, and I can confirm that the data structure is accurate. I also considered using `Combine` for asynchronous loading, but I'm not sure how to implement that effectively in this case. Is there a better way to handle loading large data sets in SwiftUI without freezing the UI? Any best practices or recommendations for optimizing this process would be greatly appreciated! I'm working on a API that needs to handle this. Any help would be greatly appreciated! This is part of a larger API I'm building. What's the correct way to implement this? Has anyone dealt with something similar?