👀 Views: 947 💬 Answers: 1 📅 Created: 2025-06-11

swift swiftui ios17

I've hit a wall trying to After trying multiple solutions online, I still can't figure this out..... I'm working with an scenario where my SwiftUI app crashes on launch with an 'EXC_BAD_ACCESS' behavior. This started happening after I updated my Xcode to version 15 and my deployment target to iOS 17. I have a simple ContentView that initializes some data in the `init` method, and I suspect the scenario might be related to how SwiftUI handles state initialization. Here’s a snippet of the ContentView: ```swift struct ContentView: View { @State private var items: [String] init() { self.items = loadItems() // This function retrieves data } var body: some View { List(items, id: \.self) { item in Text(item) } } } ``` The `loadItems()` function fetches data from a local JSON file, and here’s how it's defined: ```swift func loadItems() -> [String] { guard let url = Bundle.main.url(forResource: "items", withExtension: "json") else { return [] } do { let data = try Data(contentsOf: url) let items = try JSONDecoder().decode([String].self, from: data) return items } catch { print("behavior loading items: \(behavior)") return [] } } ``` I’ve added behavior handling in `loadItems()` and am checking that the JSON file is included correctly in my project settings under "Build Phases". I also verified that the file is accessible at runtime. Even after refactoring, the crash continues. I’ve tried different approaches to initialize the `items` property, like using `@StateObject` with a view model, but the crash still occurs. Interestingly, the app runs perfectly fine in the simulator but crashes when I test on a physical device. The crash log points me to `EXC_BAD_ACCESS`, which is usually indicative of a memory scenario. Would anyone have insights into what's causing this behavior or how to properly initialize state in SwiftUI with the latest updates? Any suggestions or best practices would be greatly appreciated! This is part of a larger application I'm building. Has anyone else encountered this? This is for a desktop app running on Windows 10. Any examples would be super helpful.