Quick pulse check on review times... I have an app submitted that triggered a question related to login credentials needed. I have responded, opened up a case with support to expedite the process and still have not made any progress. Hoping someone from Apple can provide next steps, I'm at a loss at this point.

I have noticed a strange bug with TabView in the settings window of an macOS app. When text is typed into a textbox, the icon jiggles a little bit, but ONLY on a non-retina monitor (1920x1200 in my test). Some icons jiggle, others don’t. Below is code for the gearshape which exhibits this behavior. “sparkle” doesn’t. Very odd. Tried on macOS 15.0.1, Xcode 16. You can see it in action here https://imgur.com/a/huCw7sN // App file @main struct TabViewJiggleApp: App { var body: some Scene { WindowGroup { ContentView() } Settings { SettingsView() } } } // Settings view struct SettingsView: View { @State private var input: String = "" var body: some View { TabView { TextField("Enter text", text: $input) .tabItem { Label("General", systemImage: "gearshape") .font(.system(size: 20)) } } } }

I’ve noticed a strange bug in Xcode 16 and Swift. When a preview is rendering and hasn’t finished yet and you run an app to debug, Xcode is launching two instances of the app. Has anyone else noticed this issue? If you let the preview finish rendering before running the app, this doesn’t happen. Very odd.

Hi all: I am experimenting with Finder extensions. I’d like to be able to add a context menu to all folder locations. I believe the code below should work, but it doesn’t. If I hard code a path, it does work. Any tips on what I am missing? Thanks! // Doesn’t work FIFinderSyncController.default().directoryURLs = nil // Works for user folder var myFolderURL = URL(fileURLWithPath: "/users/exampleuser") FIFinderSyncController.default().directoryURLs = [self.myFolderURL]

I’ve noticed a strange bug in Xcode 16 and Swift. When a preview is rendering and hasn’t finished yet and you run an app to debug, Xcode is launching two instances of the app. Has anyone else noticed this issue? If you let the preview finish rendering before running the app, this doesn’t happen. Very odd.