missing package product

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).

Hi Quinn @DTS Engineer I am curious if my post is missing any information needed to troubleshoot my issue. I searched through the forums and online and haven't found my specific issue anywhere. The more I think about it I come to the following: true peer to peer with no wifi network works with iOS devices without cellular (so AWDL is used) once cellular is introduced there needs to be a wifi network because using AWDL is not an option Maybe some kind of option can be passed into the NetworkListener or when creating a NetworkConnection that would prompt apple's code to try to use AWDL if the peer to peer option is true? [quote='867952022, DTS Engineer, /thread/808917?answerId=867952022#867952022'] Share and Enjoy [/quote]

ok I've managed to get it all working correctly (following from my earlier comment) I went through the checklist posted by Apple Engineer above the TechNote checklist at: TN3186: Troubleshooting In-App Purchases availability in the sandbox | Apple Developer Documentation The thing that was blocking the products being returned in array was having not filled in ALL of the details needed on the AppstoreConnect > Business page Namely payment agreement, bank account, tax status statements etc. After I had done that, about 2 hours later, all my test calls and purchasing views were working and the whole purchase flow as usual for an iOS device See attached for Sandbox confirmation Apparently all Business info is needed even for Sabdbox transactions. HTH folks. Shout if I can add any more info

having the exact same issue as others. app store connect configuration seems to be correct, but StoreKit will not return the products