missing package product

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

The way I approach issues like this is to work backwards from the contents of the built app to understand why you received an error message, and then keep going backwards from there to see why the app was built that way. For this error, you need to inspect your built app bundle. You can do this by going to the Xcode Organizer, selecting the version of your app receiving this message, right-clicking, and selecting Show in Finder. You'll see a .xcarchive package in Finder, and you select this, right-click, and select Show Package Contents. Inside of this Xcode archive package, you'll see the folders Products/Applications/YourCoolApp.app. Right click on your .app and select Show Package Contents. We're now looking at the inner contents of your app bundle. Take a look at the contents of your Info.plist file inside this bundle, and look at the value of the CFBundleExecutable key — the value of that key is the file name of your main app binary. Does that file exist? A Missing

IAP Products are testable in sandbox without requiring submission - so they appear good for testing. That error message is from RevenueCat, recommend contacting them to understand more about their error message and resolution.

Signing a distribution USB or PCI DEXT The issues described above mean that the standard Xcode GUI flow cannot be used to directly export a distribution release of a USB or PCI DEXT. Here is that flow I've found that will work: Note: The instructions below reference macOS-specific documentation, but the flow I'm describing was actually tested using an iOS project. Start by building the final version of your DEXT. On the portal, generate and download a provisioning profile for whatever environment you're going to try to build. Generate a profile for both the DEXT and the app it will be embedded in. Rename the DEXT profile you downloaded in #2 to embedded.provisionprofile”. Show the packaged contents of your DEXT and replace the existing embedded.provisionprofile (development profile) profile with the file from #3 (the release profile). Use this command to resign the DEXT with the final entitlement configuration you'll be shipping. See the Sign each code item section of Creating distribution-signed cod

I have the exact same issue and setup as the OP. All configured as per the Apple docs. Consistently getting zero products returned. Plus, on real device Settings > Developer > Sandbox > Manage > Initiate Purchase fails with incorrect Bundle and/or Prodict ID, but says Could not complete at this time, please try later with correct Bundle & Product ID. Later being 3 days so far for me... Any help please?