Swift 6

I figured out some further details: When I get a file or folder URL from the picker, I need to call startAccessingSecurityScopedResource on it first prior to converting it to a bookmark. If I don't do that and try to convert that URL to a bookmark, I am seeing this error in the console: [ERROR] getattrlist(/7{34}3/D{7}s/2{8}2/N{2}1/0{8}7/1{6}3/2{69}0.png) = 1 However, the call to make a bookmark: url!.bookmarkData(options: [], includingResourceValuesForKeys: nil, relativeTo: nil) doesn't return an error. Basically, yes, that all makes sense in terms of what's happening in the lower-level system. The situation isn't something I can easily describe, but the practical description is that the way the iOS's different file access control systems overlap means that your code can end up working that really shouldn't work. A few quick suggestions here: If it's feasible, I'd recommend testing your code as a native macOS app (not the simulator or in compatibility mode). macOS is better at enforcing the right be

Hello, Quartz Debug is available as an additional tools package for Xcode. For example, Additional Tools for Xcode 26 beta 6 contains: This package includes audio, graphics, hardware I/O, and other auxiliary tools. These tools include AU Lab, OpenGL Driver Monitor, OpenGL Profiler, Pixie, Quartz Debug, CarPlay Simulator, HomeKit Accessory Simulator, IO Registry Explorer, Network Link Conditioner, PacketLogger, Printer Simulator, 64BitConversion, Clipboard Viewer, Crash Reporter Prefs, Dictionary Development Kit, Help Indexer, and Modem Scripts.

Thank you for your help! I put this code above the code already mentioned. inline-code struct ContentView: View { var body: some View { Button(Tap Me) { // Action to perform when the button is tapped print(Button was tapped!) startAccelerometer() } } func myFunction() { // Your Swift code to be executed print(myFunction was called!) } } `inline-code` I get an error message saying: Cannot find 'startAccelerometer' in scope

Well, I don't know what I'm doing wrong. I'm using Xcode 26 Beta 6 on a macOS 26 Beta 6 VM, with macOS 15.6.1 as the host. I can build the TahoeIconsTest project, pointed to by @superpixel, and it works just as expected, the LG icon is used on macOS 26 and the old icon is used on 15.6.1. I do note that the .icns and .icon files are not in the app bundle , but there is a .car file. The Info.plist only has CFBundleIconName set (to AppIcon). However, I'm just not able to replicate this outcome with my own app. I added the secret flag and all the other asset compiler options are the same as the test project. But my build has all three files, .icns, .icon, and .car in the bundle, and my Info.plist file has both CFBundleIcon* parameters set to AppIcon. The result is both OSs use the old icon. I just can't see what's different.

I figured out some further details: when I get a file or folder URL from the picker I need to call startAccessingSecurityScopedResource on it first prior to converting it to bookmark. If I don't do that and try to convert that URL to bookmark I am seeing this error in the console: [ERROR] getattrlist(/7{34}3/D{7}s/2{8}2/N{2}1/0{8}7/1{6}3/2{69}0.png) = 1 however the call to make bookmark: url!.bookmarkData(options: [], includingResourceValuesForKeys: nil, relativeTo: nil) doesn't return an error. For a folder URL it's even less visible: no error from the call (same as for file URL) but also nothing in the console as a hint. Later on (perhaps on a different lunch) when I read a bookmark (file or folder) I don't need to call startAccessingSecurityScopedResource on it (not sure if that's intentional behaviour or not).

Amazing! Thanks @superpixel! Adding the secret undocumented --enable-icon-stack-fallback-generation=disabled to the ASSETCATALOG_OTHER_FLAGS build setting does work on Xcode 26 beta 6. What I do is enable this, disable Include all app icon assets and copy a separately compiled AppIcon.incs (with the legacy icons) to the Resources folder while making sure the CFBundleIconFile is in the Info.plist pointing to this file - this results in the correct icon showing up on older macOS versions, while Tahoe uses the Icon Composer variant. This should work on macOS (not sure if works for App Store, but my app is not an App Store app, so it does not matter). An other way is to have Include all app icon assets which generates the proper variants in Assets.car, but it bloats the bundle size somewhat (especially as I have some assets that depend on build configuration and this option makes all those into the bundle) - this might be the proper way though. Hope Apple fixes this properly though or add least adds a pr

FWIW, I'm getting this on Xcode 16.4 with no Swift Package Manager. The error alert will popup in groups of 5 or 6. All the buttons just close the alert and lead to another one.

[quote='854958022, KrishnaveniNalka, /thread/796810?answerId=854958022#854958022, /profile/KrishnaveniNalka'] If I install the Transparent Proxy or VPN payload MDM profile first [/quote] OK, but why are you doing things in that order? If I were investigating this issue, I’d do the following: Create a trivial container app A with a dummy transparent proxy PA. Set the handle-new-flow method to log the flow details and return false. Clone the app to form container app B with dummy transparent proxy PB. Install both on the Mac. Activate both of their system extensions, but don’t install any network configurations. Push an MDM proxy with a configuration for PA and PB, and the Order property set on both. Do some networking. Remove that configuration. Repeat step 6 with the Order property reversed. Do some more networking. The log entries from steps 7 and 10 will tell you whether the Order property is doing its job. This will either work on not. If it doesn’t work then you’ve clearly isolated the problem an

@DTS Engineer thank you for these suggestions. I've added the full crash report from Crashlytics to this post. After enabling the launch argument you suggested, I managed to reproduce the crash in the debugger once, so that's some progress. After enabling Swift 6 and complete concurrency checking, I got some build errors in the class owning the ModelActor. Wherever I accessed the ModelActor, I got this error: Sending 'self.localStorage.some' risks causing data races. As mentioned in my original post, the ModelActor conforms to a protocol because I am using another type of storage in iOS 16 which doesn't support SwiftData. This protocol didn't require that conforming types were Actors, leading me to suspect that the class owning the ModelActor didn't treat it as an actor, because it only know about the protocol. Adding the Actor requirement to the protocol, removed the build errors in the owning class. Now, I have to ship this change to confirm that it actually fixes it, since I cannot reliably reprod