missing package product

Just so we’re clear, ObservableObject isn’t part of Observation but part of Combine. I tried this out here in my office: Using Xcode 26.0.1, I created a new project from the macOS > Command Line Tool template. I changed main.swift to this code: import Combine class XYZ: ObservableObject { } I chose Product > Build and it compiled just fine. I’m not sure what’s going on in your case but it’s clearly context dependent. My advice is that you repeat the above steps to see if you can get the basics working. After that you can then explore why your original project is behaving differently from this test project. [quote='802686021, Gatti, /thread/802686, /profile/Gatti'] after updating to 26.0.1 [/quote] Upgrading from what? Xcode 26.0? Or Xcode 16.4? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hello, Could you tell me more about these watchOS targets? My primary curiosity is how they are able to build successfully even during a normal build, if their dependencies do not support watchOS. To more directly address your questions, Localization Export and Import are intended to cover all localizable content in the sources of the entire project or workspace. This way, a single xcloc/XLIFF file can be used for the entire project. Is directly parsing .xcstrings files and generating XLIFF an acceptable alternative, or does this miss important metadata that -exportLocalizations would include? This could work for your use case, but it is not a recommended flow and could miss a lot of things that Export would give you. Also, the xcstrings format is not guaranteed to remain stable from version to version. When you Export with Xcode (GUI or CLI), Xcode does the following: Includes strings from existing .xcstrings, .strings, and .stringsdict files in your project. Extracts localizable strings fr

Assuming I have existing subscribers from country X, if I remove the availability of that subscription in country X, will I still be able to charge those subscribers in the next billing cycle? Existing subscribers won't be charged. When you remove an in-app purchase product from sale, customers that already purchased the product will retain access. Those transactions will be available with StoreKit and in App Store Server API. You are expected to continue providing the purchased content to their subscribers.

I’ve seen requests for this go by in the past, and I think I know the right process, but this is definitely more of a Kevin thing than a me thing. I’m going to run this past him before I say anything definitive. Not if I say something first... Is this a managed entitlement? It is, but the request volume is low enough that it's never been integrated into the developer portal. You can submit a request by submitting a bug report with the following format: Start by clicking on the appropriate OS button - “macOS” In the “Descriptive Title” field, enter Request for Entitlement - com.apple.developer.usb.host-controller-interface In the “Problem Area” field select “USB” In the “Type of Feedback” select “Other Bug” Finally, in the “Describe the Issue” section enter the details regarding your planned use for this entitlement. As part of that, please make sure you include the following: Your team ID A general overview of the product you intend to make. Links to any marketing material you have for your product

@DTS Engineer What's the point of filing a bug report? Will it actually get fixed? I'm asking a serious question because I've already filed several iOS/iPadOS 26 bug reports related to UISplitViewController and UIKit. Several were reported against beta 1. Those bug reports include trivial sample apps and step-by-step instructions demonstrating the issue. None have been fixed as of iOS/iPadOS 26.0 GM. I also have several outstanding bug reports for broken functionality about UISearchController/UISearchBar under iOS/iPadOS 26. Again, several since beta 1. All include trivial test apps that demonstrate the issue. Again, none have been fixed. All of these outstanding issues are impacting my app. I'm very frustrated and disappointed. I'm sorry but I no longer have the ambition to file more bug reports that will never be fixed. I truly hope Apple gets back to the days of it just works. That era seems to be lost at the moment. Every year iOS and others are updated with lots of new features and lots of new b

Thanks very much, Kevin. It does seem like a bit of a miss that you can send the data off-device to train a filter, but can't do so on-device, especially given all the new on-device ML support. Perhaps there's a good reason for it, but if not, I'd love to be able to do this in a future version. Best, Athul

Hi - thanks for asking. My app will download a JSON file which contains a list of image urls which are downloaded and stored in the NSCachesDirectory. I understand the NSCachesDirectory can get deleted by the OS when the app is not running, so on subsequent launch, the app will check for the presence of these files in NSCachesDirectory and will redownload them if they are not available. This has worked pretty reliably in production for nearly two years. With tvOS 26, there are now inconsistent and sporadic instances when the app exhibits behavior as if these files have been deleted. ie. the images are either missing from the playlist page, or the app uses an onboard backup failsafe JSON file to populate a playlist with temporary data if it cannot find or load the JSON file. I suspect something is getting corrupted because once this issue occurs, the only way to get the app to perform normally again is to delete and reinstall the app. Simply relaunching the app will not fix the issue, as prog

I have a few resources to share with you: Placing content in a bundle explains how bundles should be structured. Creating distribution-signed code for macOS and Packaging Mac software for distribution explain how to manually sign code. Embedding nonstandard code structures in a bundle offers advice on how to deal with non-Apple code structures, like the ones used by Python. You have a couple of choices here: You can strictly follow the rules in Placing content in a bundle, which is a bunch of extra work right now but will likely work better in the long term. You can bend those rules by simply signing your code as it’s currently structured. Based on the script you included, it looks like you’re attempting the second approach. It’s likely you’ll be able to make that work, but that script will need significant enhancement. For example, Creating distribution-signed code for macOS explains that you need to sign code from the inside out from a dependency perspective, and your script is doing it from a file

[quote='860350022, Michael8619, /thread/802183?answerId=860350022#860350022, /profile/Michael8619'] after 3.5 days of waiting. [/quote] Blergh. Lemme know if you see such a long delay in your subsequent notarisation requests. Normally I see follow-up requests go through quickly, but that’s after a successful notarisation. I’m curious to see if your unsuccessful notarisation still allowed the system to ‘learn’. [quote='860350022, Michael8619, /thread/802183?answerId=860350022#860350022, /profile/Michael8619'] I must have missed some files in mine as I just received invalid on all my files [/quote] OK. If you’re unable to resolve this, I’d be happy to take a look. My only ask is that you start a new thread with the details, so we can leave this thread focused on the “in-depth analysis” issue. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com