@bergersilvio DataService needs to be a class for it be an @ObservableObject. Can you try storing dataPoints directly inside DataService and ensure it is @Published? I feel that should help. If that doesn't work if it is ok with you could commit your code (or take a backup) then comment out all unnecessary portions till you can come down to a minimum reproducible code. Commenting out will help you isolate the issue. Then you could create a simple POC so that others can test.

@bergersilvio, I meant in your SwiftUI code use only @Published properties don't use something like DATA.depots.dataPoints use DATA.dataPoints instead. Good luck

@pabloconnell hope that helps

@bergersilvio call objectWillChange.send() in your model when you want the View to change.

@Claude31 The main issue is with the URL string. Question is whether this opening "x-apple.systempreferences:com.apple.preference.security?Privacy_Calendars" URL would be considered as accessing private API in the Apple Store. Original code I posted works but not sure it is allowed.

@eskimo Thanks a lot, just curious how in the mac Maps app when location permission is not granted, when the user taps on current location button it shows an alert which opens the Privacy & Security pane

@eskimo I forgot to mention I have enabled Calendar under Capabilities and added INFOPLIST_KEY_NSCalendarsUsageDescription which prompts the user for Calendar access when needed

@eskimo, Hoping one day macOS System Settings has app level settings, IMHO that would be a safer option (just like in iOS) so that devs don't abuse the option. Sorry just wishful thinking, thanks once again

@eskimo could you have a look at this?

@darkpaw sorry I should have mentioned earlier, it wouldn't work in the following logger.debug("Item name = \(itemName, privacy: .public)"), see my updated "Non-sensitive logging (Public)"

@darkpaw Thanks a lot, I feel it clutters the Xcode debugger output and I find it a bit cluttered hard to read. Is there a way in Xcod to color different for different logger messages (some way ti differentiate: debug / log / error)

@darkpaw Thanks a lot! I will stick with Apple's Logger, there is no way I can build anything remotely as efficient or robust. They do a lot of good things, thanks

@eskimo Thanks a lot! well written article and I like the reference to friendship. Definitely the advantages to using Logger far outweigh the my small preferences. So I will stick with the logger. My wish list is Xcode some day provides a way to customise how these messages are being displayed (more around timestamp being wrapped). It is definitely a priority .... a nice to have. Definitely console app does a good job in the meantime. Thanks once again

@mtsrodrigues Thank you so much!!!!! Made my day!

@ortwin thank you so much!! Just to add ensure you are using color depth as 16 bits / channel as well (along with "Assign" Display P3) This is the best way to fix the color for screenshots taken from the simulator.