Yes, by now I'm fairly sure it's a bug. I was able to reproduce the issue in all beta versions of iOS 18. The error is not present in the iOS 17 line. I've submitted a report in the Feedback Assistant with a sample Xcode project. FB15221588

The issue only occurs with iOS 18, but not with iOS 17.

unfortunately This modifier has no effect on iOS.

Hi, you can use the environment modifier with the argument layouDirection and value rightToLeft like this: .environment(.layoutDirection, .rightToLeft) VStack { Image(systemName: "chart.bar.doc.horizontal.fill") .imageScale(.large) .foregroundColor(.mint) // right to left sfsymbol Image(systemName: "chart.bar.doc.horizontal.fill") .imageScale(.large) .foregroundColor(.mint) .environment(\.layoutDirection, .rightToLeft) } for more information https://developer.apple.com/videos/play/wwdc2022/10107/

Hi Noel, I would like to help you. Unfortunately, the code is incomplete, so I can only assist to a limited extent. Please make sure to use the 'Environment' during observation. I recommend watching the video https://www.youtube.com/watch?v=jD6c9y8CFGQ&t=1793s. Regarding the first error in 'HomePageView.swift:63:37,' 'Missing argument for parameter 'forUser' in call,' and the function 'getUserData' expects a 'forUser' parameter, which you do not pass when calling it in the 'onAppear' block. I'd be happy to assist you further if you post the entire code here.

I have experienced the same behavior and have added a button to regularly delete the data. I feel that during the development, when the data structure changes frequently, the application becomes buggy. Perhaps this might help you. func removeStoredData() { do { try context.delete(model: WorkoutModelItem.self) } catch { fatalError(error.localizedDescription) } } Before you start user testing, for example, in TestFlight, you can disable the button again.

https://developer.apple.com/documentation/SwiftUI/Building-a-document-based-app-using-SwiftData

how can I report the bug to apple. I have the same issue. I was hoping that 13.3.1 would be better. unfortunately not. Same error same report?

same problem here

Hi, I have the same problem with Xcode Version 13.3. I will downgrade to older version and will report about it

I recommend Paul Hegarty from Stanford in YouTube