Hi Quinn, thanks a lot for your help. I created an empty Xcode project with the "Command Line Tool" template, pasted your code, and ran the built executable in the Terminal. When passing the pids for all the trustd processes I see in Activity Monitor it always returns the expected path, /usr/libexec/trustd. But then I created an empty Xcode project with the "App" template and created a main.swift file again with your code, and when running the built App/Contents/MacOS/app in the Terminal, I get the same error that I mentioned before: Error Domain=NSOSStatusErrorDomain Code=100001 "EPERM: Operation not permitted". Do I need to add special entitlements in order to make it work?

Yes, that's the entire code in the project.

I don't know the direct solution to your issue, but I'm using appstoreconnect-swift-sdk on GitHub to interact with the API. I found it quite easy to upload images, but feel free to ask if you're having problems.

Did you just download the Ventura installer and ran it? Because as I wrote in the original post, I wasn't able to install Ventura either.

I still have to come up with a solution myself.

Could it be that you sent the wrong link for Slovak? It seems to be the same for Finnish. Otherwise it really seems like something's not working. Have you double-checked that selecting the respective language in App Store Connect shows the expected text? If that works as expected, I would use the Contact link at the bottom of the App Store Connect website and explain the issue.

Could you post the URLs that you're using to see the respective App Stores?

Find below my sample code that shows how it's impossible to associate any custom data with a path item. PathControl.pathItems.didSet is called only once when explicitly setting them in loadView(), and in the action selectPath(_:) the path items are not of my custom subclass PathControlItem but are again NSPathControlItem. They change their address on every click, and finding the clicked path item in the pathItems array always returns nil even if by comparing the logged addresses it appears to be there. class ViewController: NSViewController { override func loadView() { let pathControl = PathControl() pathControl.action = #selector(selectPath(_:)) pathControl.pathItems = ["a", "b", "c"].map({ title in let item = PathControlItem() item.title = title item.customData = title return item }) view = NSStackView(views: [pathControl]) } @IBAction func selectPath(_ sender: NSPathControl) { print("click", sender.clickedPathItem!.description, (sender.clickedPathItem as? PathControlItem)?.customData, sender.pathItems.description, sender.pathItems.firstIndex(of: sender.clickedPathItem!), sender.pathItems.firstIndex(where: { $0.description == sender.clickedPathItem!.description })) } } class PathControl: NSPathControl { override var pathItems: [NSPathControlItem] { didSet { print("didSet", pathItems) } } } class PathControlItem: NSPathControlItem { var customData = "" }

The documentation in the header file for NSPathControlItem also states: "NSPathControlItem should not be subclassed." I tried doing so nonetheless, but sender.clickedPathItem as! MyPathControlItem fails with the error Could not cast value of type 'NSPathControlItem' (0x20ae78870) to 'MyPathControlItem' (0x1005c0688). So it seems like any custom subclass is replaced again with NSPathControlItem.

Yes, on the Mac in a sandboxed app. It succeeds.

I'm experiencing the same warning when using a NSOutlineView without SwiftUI, but only a few rows. I opened a new topic here.

I asked the same exact thing in Feedback Assistant 4 years ago, and they told me that they have no plans on making old macOS installers available. Apparently they have no interest in allowing developers to support older macOS systems, which, assuming that their main interest is maximizing profit from Mac sales by pushing people to abandon old Macs that don't support the software they need anymore, totally makes sense.

I was wondering about the same thing. The release notes for Xcode 14 say only macOS 10.13 and newer are supported, but running all my projects that have deployment target macOS 10.10 works fine. Except for one of them, the only one which has a dependency installed with Swift Package Manager, which now complains that the dependency, which got its last commit over 1 year ago, only supports macOS 10.13 and newer (this was working fine with Xcode 13).

When running my FinderSync target in Xcode, in the debug navigator it reads "Waiting to attach". I have to manually select "Debug > Attach to Process > My FinderSync target" (listed at the top under Likely Targets). I don't understand how Apple never cared to comment on this issue, which could easily be avoided by improving Xcode, and chose to let us find this out by ourselves.

Thank you for the workaround. Yes, this issue was solved, according to the message I got in Feedback Assistant, with iOS 14.5.1.