missing package product

Can someone please explain why Mac app packaging is so farcically convoluted? Windows app packaging can be picked up in an hour or so. But I've spent longer trying to fathom how to package the Mac version than I did building the app. And it's not done with me yet. Every single line of code requires a deep dive into a new, unrelated skillset. So, it’s sidebar after sidebar. Kafka’s ‘The Trial’ comes to mind. Why does it have to be like this?

I'm suddenly receiving zero products from SKProductsRequest, even though this setup previously worked without issues. The debugger shows that both of my product identifiers are now being returned under invalidIdentifiers, and response.products is empty. I’ve confirmed the following: There are no pending agreements in App Store Connect. The subscription is active and configured correctly. The product identifiers match exactly with what’s defined in App Store Connect. Here is the delegate method I'm using (unchanged from when it previously worked): extension UpgradeViewModelProvider: SKProductsRequestDelegate { func productsRequest(_ request: SKProductsRequest, didReceive response: SKProductsResponse) { if response.products.count > 0 { delegate.send(.onProduct(response.products)) } } } Since everything was functioning before, I’m trying to understand what may have caused the identifiers to suddenly be marked as invalid. Any guidance or suggestions on what to check next would be gre

Provisioning profiles created for my App ID are not including the Push Notifications capability, even though Push Notifications is enabled in the App ID configuration in Apple Developer Portal. I have enabled Push Notifications for my App ID (com.abc.app) in the Apple Developer Portal. The capability shows as enabled and saved. However, when provisioning profiles are generated (either manually or through third-party tools like Expo Application Services), they do not include: The Push Notifications capability The aps-environment entitlement This results in build failures with the following errors: Provisioning profile *[expo] com.abc.app AppStore [timestamp] doesn't support the Push Notifications capability. Provisioning profile *[expo] com.abc.app AppStore [timestamp] doesn't include the aps-environment entitlement. Steps Taken ✅ Enabled Push Notifications in App ID configuration (com.mirova.app) ✅ Saved the App ID configuration multiple times ✅ Waited for Apple's systems to sync (waited 5-10 minutes) ✅ Remov

Like any good developer, I try to add tests where I can. The AgeRangeService.AgeRange type does not provide an initializer. I know the routine, create an interface or a simple struct that I control and use that instead. Thanks to extensive time with frameworks like Core Bluetooth or Core Location, this is a well understood practice (looking at you CBPeripheral...). Great I'll make my own 'AgeRange' struct. Make it Hashable, make it Sendable, use the framework types as properties. Scratch that, most of the properties on AgeRangeService.AgeRange type are not Sendable and many are also not Hashable. This is proving to be challenging. I hope to open source my little Swift Package wrapper library for DeclaredAgeRange which will add types with full Hashable and Sendable conformance. I hope Apple updates the API and makes this obsolete. I don't see why these simple types can't be Hashable and Sendable. They're structs, enums, and OptionSets (structs). FB20959748 - DeclaredAgeRange: DeclaredAgeRangeAction is

I'm making a wrapper library to abstract away some of the 'missing platform support' of DeclaredAgeRange until hopefully it expands to additional platforms. When I'm trying to fully enumerate all of the cases of AgeRangeDeclaration, which they all state available starting 26.0 (mysteriously added in Xcode 26.2 beta), the app crashes due to a missing symbol at launch time. This happens both for Xcode 26.1, 26.2 beta 2, and matching Xcode Cloud builds. So I've isolated it beyond doesn't work on my machine. I just made a handful of crashes and attached a sysdiagnose to a fresh feedback. FB21121092 - DeclaredAgeRange: Eligibility property and new declaration cases unavailable on iOS 26.1 device contradicting documentation - causes runtime symbol not found crash If anyone is curious what these crashes look like I've attached the DiagnosticPayload.jsonRepresentation() generated from one of my favorite frameworks, MetricKit. Very clearly articulated in the diagnostic metadata you can see the symbol

I've been writing about the DeclaredAgeRange a bit on LinkedIn and now it is time to take to the developer forums. In my efforts to prepare my apps for new local requirements, I've run across some rough edges. The DeclaredAgeRange API is missing on several platforms, and extension types. First and foremost, watchOS. An Apple Watch is a clear single user platform and for standalone apps, the DeclaredAgeRange being absent is felt by developers. FB20954931 - DeclaredAgeRange: Framework not available on watchOS making compliance a challenge for watchOS standalone apps In the same vein of thinking, while users on Apple Vision Pro are far fewer numbers than Apple Watch, it is also a miss. The tricky part would be testing on the simulator. So far I haven't gotten the simulator and sandbox testing to work and give real values across any platform. I don't think an Apple Store will let me try my app out via TestFlight on their devices and they're still too expensive to reasonably buy for most develope

Hi everyone, I’m seeing a red X icon beside Certificates, Identifiers & Profiles under my Role settings in App Store Connect, even though my account is listed as Admin. My question is: What does the red X next to “Certificates, Identifiers, & Profiles” mean for an Admin account? Does this indicate a missing permission, an issue with my Apple Developer Program membership, or something else? Im on a Personal 99/year membership

Hello, I’m contacting you for assistance regarding an App Review issue that our company is currently facing. Background Several months ago, a former employee submitted an early prototype of our app using his personal Apple Developer account. That submission was never approved, and after the employee left the company, he removed the app from his account. It is no longer available on the App Store and no longer listed under that account. Recently, we rebuilt the product completely — new UI, new codebase, and a fully updated design — and submitted it under our company’s official Apple Developer account. Issue Our recent submission was rejected with 4.3 – Spam, indicating that our app is considered a duplicate of another existing app. However, the only similar app is the old prototype submitted several months ago by the former employee, which was removed and never published. It seems likely that our submission is being linked to that previous prototype, even though it no longer exists and was submitted u

I'm developing in Objective C with Xcode on a Mac exclusively to run on Mac and all of a sudden when I try to run I get the message: a build only device cannot be used to run this target. If I go to the destination folder, the newly built app is there and runs from Finder, I just can't get it to run from within Xcode, which is inconvenient for testing. What setting am I missing or has changed? Up to now I could build and run with no problem.

Hi, I’m completely stuck with a very strange CloudKit problem that started recently and has now killed all iCloud sync for a live production app. What is happening Production container: iCloud.gainzCloud (created ~11 months ago, has been working perfectly until now) In Xcode 26.0 (17A321): → Signing & Capabilities → iCloud is enabled → Container correctly shows as iCloud.gainzCloud → App builds and runs on device/simulator with zero provisioning or container errors CloudKit Dashboard (https://icloud.developer.apple.com/dashboard/): completely blank – “No containers found” Result: CloudKit sync is dead for every user (development + production environments) What I know for sure Apple Developer Support confirmed the container iCloud.gainzCloud still exists and is correctly attached to my Team ID on their backend Personal iCloud (Mail, Notes, Photos, etc.) syncs perfectly on the same Mac / same Apple ID under macOS Tahoe 26.1 I have NOT changed the password on either the Apple ID or

The app review prompt on iOS/iPadOS 26.1 has the Not Now button greyed out: On iOS/iPadOS 26.0, this was working: Before filing a radar, is there anything I'm missing? The only way to dismiss it is to tap a star rating and then a Cancel button appears which lets you dismiss it without reviewing.