missing package product

Hi Ed, Thank you very much for your previous guidance. Our current app requirement is to allow users to run a Shortcut, share an image to our app, and then immediately receive some chat-based suggestions after we process the image. When using App Intent, I noticed that we cannot process the image directly within the invoked UI. It appears that this is restricted by Apple’s privacy protections—any attempt to handle the data immediately results in the background privacy indicator showing a blocked status. Therefore, App Intent does not seem to meet our need to process user-provided images directly. Following your advice, I added an Action Extension to the project. This successfully adds our app to Shortcuts as an available action. However, when I try to use the “Share with App” feature from the share sheet, our app still does not appear in the list. The only options shown are: Notes, Health, Reminders, and Freeform. Could you help us understand why our app does not show up in the “Share with App” menu, even tho

I am having the same exact issue. I don't want to miss the deadline!

Please file an enhancement request using the Feedback Assistant so that your request can be seen by the appropriate decision makers. If you file the request, please post the Feedback number here so we can make sure it gets routed to the right team. Please note that filing an enhancement request does not guarantee Apple will add any requested functionality to Apple products in the future. However, with that said, filing an enhancement request is a good way to get your ideas in front of the folks who make decisions about that sort of thing. If you're not familiar with how to file enhancement requests, take a look at Bug Reporting: How and Why?

I built Dext with a development ID and successfully re-signed and notarized it. This time, I only notarized the Driverkit, and plan to do the installer app later. Here are the steps I tried: Signed the build using Apple Development in Xcode Re-signed the build product Zipped the build product Notarized using xcrun notarytool submit, which returned Accept. Below is a sample re-signing command. codesign --sign $CODE_SIGN_IDENTITY --entitlements --options runtime --verbose --force build/Release/.app I'll probably need to eventually create an installer app and notarize it, but I think I've temporarily resolved the recent issue of not being able to sign with a Developer ID in Xcode. If you have any issues from an engineering perspective, please let me know.

How did you discover that? I’m experiencing the same issue - the UI doesn’t redraw on iOS 26.1, but all other versions work fine. I’m at a loss as to where to look for a solution.

I identified that ExternalPurchaseLink.canOpen was returning false because StoreKit determines eligibility solely based on the storefront country of the device’s production App Store account, regardless of the sandbox Apple ID used for testing. Since the production account on the device was set to a country that does not support External Purchase Links, the API consistently reported ineligible results. After switching the production App Store account to a supported storefront, the API began functioning correctly. At this point, I am not certain whether this behavior is intentional or a potential bug.

Thanks for pointing out these issues, I have modified my snippet according to your suggestion: struct MobileProvision: Codable { static let current: MobileProvision = { guard let profilePath = Bundle.main.url( forResource: embedded, withExtension: mobileprovision ), let profileData = try? Data(contentsOf: profilePath), let statrtRange = profileData.firstRange( of: .data(using: .isoLatin1)!, in: statrtRange.endIndex.. Self { #if targetEnvironment(simulator) return Self(entitlements: Entitlements(isDebuggable: true, apsEnvironment: .development)) #else return Self(entitlements: Entitlements(isDebuggable: false, apsEnvironment: .production)) #endif } let entitlements: Entitlements enum CodingKeys: String, CodingKey { case entitlements = Entitlements } struct Entitlements: Codable { let isDebuggable: Bool let apsEnvironment: APSEnvironment enum APSEnvironment: String, Codable { case development, production } enum CodingKeys: String, CodingKey { case isDebuggable = get-task-allow case apsEnvironm

Hi Quinn, Thanks for your previous explanation. After further investigation, I realized that our Keychain item structure might be related to the issue, so I’d like to share more details in case this helps narrow down the cause. How we currently store data in a single Keychain item For the same Keychain item, we store two different business values: kSecValueData → contains the deviceId kSecAttrAccount → contains a dynamic userKey This means the item looks like this: Service: Account: // changes when user switches account Value: kSecAttrAccessible: kSecAttrAccessibleAfterFirstUnlock Potential problem we’ve discovered Because the userKey (stored in kSecAttrAccount) can change over time, our update operation may unintentionally rewrite or merge attributes in a way that leaves some users with inconsistent Keychain item metadata. For example: Version A of the app may write incorrect or incomplete attributes. Version B fixes the attributes, but existing users still keep the old item with mismatched attributes. Th

I cannot find Sandbox Testing > Age Assurance from my iPhone's Developer Settings. From the documentation: Test various age range scenarios on the Age Assurance page in iOS by following these steps: Open Settings and select Developer. Tap Sandbox Testing from the main menu. From the Sandbox Testing screen, tap Age Assurance. Choose from the available age scenarios based on your testing needs. The following image shows what I can see from my iPhone's Developer setting screen. There is no Sandbox Testing for Age Assurance. What did I missed to make the menu appear? I should also note that the iPhone is on iOS 26.2 RC. This is an iPhone SE (2nd generation).