“missing package product”

I'll have to spend a little more time playing around to properly isolate things but it looks like this might be related to it being an Xcode workspace with the two packages. If I open just the executable package in Xcode everything works as expected.

Fully seconding this, Frederik! I found this thread because I’m facing an issue with DeviceActivity thresholds not firing at all. I’m also trying to understand how this behaves in production for apps that rely on usage-threshold relocking. Have you found any mitigation or ‘least broken’ implementation pattern that improves reliability, even if there’s no true workaround? Any OS-version-specific observations would be really helpful. Thanks in advance!

I’d like a robust dev environment for this. I’m not confident cksyncengine works for sandbox users. I’m not confident cksyncengine works in Xcode simulators I’m not confident cksyncengine works in development as opposed to production iCloud. Without this confidence it’s difficult to set-up, difficult to test and difficult reporting bugs.

Seconding everything that's been said in this thread so far. The agentic coding is much laggier and overall unpredictable. I'm waiting 5-10 minutes sometimes for a response. It also seems to eat up my usage limits much faster. I'm seeing the same issues with authentication. I have to sign in to Claude multiple times per day. And I agree that hiding the thinking while it's happening leads to a lot of wasted time and tokens because I have no idea if the agent has lost its way. Appreciate you looking into this and hopefully releasing a 26.4.1 to address these issues!

I confirm that installing the Xcode.app/Contents/Resources/Packages/MobileDevice.pkg package of Xcode 26.4 (with the UI) on macOS 15.7.5 fix the installation problem of macOS 26.4 in VirtualBuddy.

I have managed to wrap a command line tool into a .app package and to test my package localization. while this works it's obviously not the idle way to test a package localization. Just waiting to see if I get any more responses from someone who has actually tried to do this. Just to recap, there is nothing special here, just a command line tool with a Localization.xcstrings file that has one sentence both in English and fr-CA.

by console, I am referring to a command line tool. Yes. I realize that. But use of the word console is triggering. It's better to say Terminal or command-line to minimize the distress of your fellow developer. My intention was to use the command line tool to test a package I am working on, as the eventual target will be a window app, I may abandon my efforts to localize my command line tool. I am using Swift Testing to unit test the package. I was hoping to hear from someone who had actually done this already. I'm not sure what you're trying to do there. I do have an app that can operate both normally and on the command line. So I can verify that it does work. But unless you have very specific requirements, and someone paying your bills for you, stay far away from any kind of command line tool on the Mac. The command line is a radically different environment and is wholly unsuitable for testing a normal app. If you want to do unit testing, I guess that's fine. You can use the Xcode debugger

I need to be direct: we are now moving into new territory. This has gone on for four months. Four months of open cases, broken contact forms, no resolution, and now an app that has vanished from App Store Connect entirely with zero explanation. The pace of this is completely unacceptable for a paid business account. The facts are not in dispute: Payment of £79 cleared my bank on 12 March 2026. I have the bank statement. The account was renewed and active. Team ID: AW699Z7G8H, Bundle ID: com.sofiqe.app, Case: 102841743378. Despite this, Apple's systems are showing my membership as expired and prompting me to pay again. This means Apple cannot keep track of what has been paid. That is not a developer error. That is an Apple billing failure. I am now being asked to pay twice for a membership I already hold, while my app has been pulled from the store, TestFlight distribution is blocked, and my business is actively losing time and revenue. I have two demands: An account-level specialist verifies the 12 M

by console, I am referring to a command line tool. My intention was to use the command line tool to test a package I am working on, as the eventual target will be a window app, I may abandon my efforts to localize my command line tool. I am using Swift Testing to unit test the package. I was hoping to hear from someone who had actually done this already.

I've found a solution. I need to delete subscription products with status Developer Action Needed and create a new one. This needs changing product id and fixing app for new ids... Apple, fix your process, it's buggy.

If an app assumes it's appending only one path component on a directory it owns (like inside a package), it may think it is safe, but it can be tricked into overwriting files at unexpected file system locations.

I was able to replicate this issue in a very simple way, within a new project created with the standard Xcode template, to which I added a Swift Package as a library (MyLibrary). This is the Package definition: // swift-tools-version: 6.3 // The swift-tools-version declares the minimum version of Swift required to build this package. import PackageDescription let package = Package( name: MyLibrary, platforms: [.iOS(.v18)], products: [ // Products define the executables and libraries a package produces, making them visible to other packages. .library( name: MyLibrary, targets: [MyLibrary] ), ], targets: [ // Targets are the basic building blocks of a package, defining a module or a test suite. // Targets can depend on other targets in this package and products from dependencies. .target( name: MyLibrary, path: Sources/MyLibrary ), ], swiftLanguageModes: [.v6] ) If the target name is equal to library name