Value of type ‘AVCapturePhoto’ has no member ‘livePhotoMovieFileURL’

Value of type ‘AVCapturePhoto’ has no member ‘livePhotoMovieFileURL’

Value of type ‘AVCapturePhoto’ has no member ‘livePhotoMovieFileURL’

Is it possible to change the default save dialog that appears when creating a document based MacOS app in SwiftUI?

Is it possible to change the default save dialog that appears when creating a document based MacOS app in SwiftUI?

I’m trying to create a function in Swift that requests the authorization for the individual and fetch the screen time app usage data of all the installed apps inside iphone device for last 24 hours. I’ve added the necessary permissions and capabilities.

I’m a little confused on when to use @StateObject/@ObservedObject and when to use @EnvironmentObject. My confusing is for when the same ViewModel needs to be used in multiple views. For instance, the code below, I need to use SomeViewModel in all four tab views. In fact, in my current app I’m injecting all my ViewModels to the @EnvironmentObjet as shown in Method 2 below, but I recenlty ran into an issue where some UI controls were not showing and realized that by removing the calls to the view models solves the issue so, I’m now wondering if @StateObject/@ObservedObject is the right choice but after thinking about it, the way I’m showing in Method 1, I’m creating multiple instances of the SomeViewModel and got me wondering if I will end up running into different issues.

I’m a little confused on when to use @StateObject/@ObservedObject and when to use @EnvironmentObject. My confusing is for when the same ViewModel needs to be used in multiple views. For instance, the code below, I need to use SomeViewModel in all four tab views. In fact, in my current app I’m injecting all my ViewModels to the @EnvironmentObjet as shown in Method 2 below, but I recenlty ran into an issue where some UI controls were not showing and realized that by removing the calls to the view models solves the issue so, I’m now wondering if @StateObject/@ObservedObject is the right choice but after thinking about it, the way I’m showing in Method 1, I’m creating multiple instances of the SomeViewModel and got me wondering if I will end up running into different issues.

I’m a little confused on when to use @StateObject/@ObservedObject and when to use @EnvironmentObject. My confusing is for when the same ViewModel needs to be used in multiple views. For instance, the code below, I need to use SomeViewModel in all four tab views. In fact, in my current app I’m injecting all my ViewModels to the @EnvironmentObjet as shown in Method 2 below, but I recenlty ran into an issue where some UI controls were not showing and realized that by removing the calls to the view models solves the issue so, I’m now wondering if @StateObject/@ObservedObject is the right choice but after thinking about it, the way I’m showing in Method 1, I’m creating multiple instances of the SomeViewModel and got me wondering if I will end up running into different issues.

I’m a little confused on when to use @StateObject/@ObservedObject and when to use @EnvironmentObject. My confusing is for when the same ViewModel needs to be used in multiple views. For instance, the code below, I need to use SomeViewModel in all four tab views. In fact, in my current app I’m injecting all my ViewModels to the @EnvironmentObjet as shown in Method 2 below, but I recenlty ran into an issue where some UI controls were not showing and realized that by removing the calls to the view models solves the issue so, I’m now wondering if @StateObject/@ObservedObject is the right choice but after thinking about it, the way I’m showing in Method 1, I’m creating multiple instances of the SomeViewModel and got me wondering if I will end up running into different issues.