Thanks; That will work; I was just hoping to be able to use the simulator version of Beta 8 instead of installing it on my devices right away.

I have much more luck with Tab inside TabView with iOS18. Still some issues, but I suspect I will get those more easily going forward.

I went to a WWDC25 SwiftUI Lab regarding this issue. The suggested known workaround was to wrap the 2nd property change in a DispatchQueue.main.async call so that it happens on the next turn of the run loop. You can see my change here: https://github.com/bolsinga/site/pull/1024

I've worked around with an App Bundler wrapping my CLI. However I saw this post today, and I think it is relevant for anyone coming across this Forum post in the future. https://steipete.me/posts/2025/applescript-cli-macos-complete-guide

Hi. Basically I want the state of the iOS app to be shared with CarPlay, if the iOS app is already launched. I also want the CarPlay state to be shared with the iOS app if iOS is launched later. If there is no state to share, each will initialize its own state. Will CPTemplateApplicationSceneDelegate be "launched" w/o starting the iOS App / UIApplicationDelegate? As an example, I see Apple Maps will share the selected route if you loaded it at home before getting in the car. On the iOS app, I see the Apple Maps steps UI if the CarPlay is navigating. I think it boils down to wanting to know how to transfer data from a SwiftUI App to UISceneDelegate. I assumed it would be via the UIApplicationDelegate. The CoastalRoads CarPlay example doesn't use SwiftUI, and it has TemplateManager.shared. I was hoping there would be a way to pass data around via the app and scene delegates w/o a .shared. Thanks for replying!

Thanks for your suggestion of changing my Mac's Time Zone to reproduce the bug! I filed FB15767197 with a simple program attached to that bug. Program demonstrating the problem. The bad Dates occur with both MusicKit and iTunesLibrary, so hopefully the underlying bug can be fixed for them both.

[quote='812604022, DTS Engineer, /thread/767837?answerId=812604022#812604022'] That depends on exactly what it’s doing wrong. Do you have code for that library? [/quote] No, it's iTunesLibrary in macOS. All of my code is on my GitHub. Adding to the debugging clues, last night it returned dateModified values back in line with what they were before the DST change! I'm guessing that somewhere deep in that code it was not fully aware DST has changed. Strangely, the dateAdded changes remain. I know this will sound crazy, but I think iTunes has had this bug since at least 2007, when I started dumping its data regularly!

This appears to be fixed in newer OSs.

Thanks @DTS Engineer (Quinn)! I used your suggestion and it worked. I made a wrapping App Bundle that lets it work again and again when loaded by my LaunchAgent.

moved to original post

moved to original post

Fixed w/ proper annotations in iOS18.

With the same code, the warning is gone in Xcode 15.4, where I target x.5 releases of iOS and macOS.

I think I have just about solved the problem. My shell script launched both my own binary and git. I have updated my binary to launch git via Process. Now my launchd plist launches my binary itself instead of using the shell. It has asked for UI permission to run each time (3 times now). I'm not sure why my answer hasn't been sticky yet...

Aha. My shell script is sandboxed. Not sure if I can add permissions to a shell script. I am going to try to create a Swift command line tool that uses Process to invoke git. Updates to come.