missing package product

tried to restore purchase Are you calling restoreCompletedTransactions() to restore your purchases? If yes, this method doesn't return in the following situations: All transactions are unfinished. The user did not purchase anything that is restorable. You tried to restore items that are not restorable, such as a non-renewing subscription or a consumable product. Your app’s build version does not meet the guidelines for the CFBundleVersion key.

From restoreCompletedTransactions(): This method has no effect in the following situations: All transactions are unfinished. The user did not purchase anything that is restorable. You tried to restore items that are not restorable, such as a non-renewing subscription or a consumable product. Your app’s build version does not meet the guidelines for the CFBundleVersion key.

Hello - When offering in-app purchase subscriptions, it is common to offer different subscription periods for the same level of access - where the only differences are price and duration of subscriptions (e.g. monthly, quarterly, and annual.) If the access entitled by various subscriptions is the same (that is, a monthly subscriber has access to all of the same content, features, etc. as an annual subscriber), it is best practice to assign all of those subscription products to the same subscription group in App Store Connect, as documented here - including the assignment of subscription levels. This will ensure correct handling of upgrades, crossgrades, and downgrades, as documented here, and prevent customers from having more than one active subscription at a time. While developers can control how and when to merchandise subscription products in their app, it is not possible to restrict customers from switching between available products in the same subscription group from their Ma

The Advanced Commerce API utilizes two generic product identifiers that you configure within App Store Connect. A Consumable Product Type, which can be utilized for all one-time purchase products. An Auto-Renewable Subscription, which represents all your products in your catalog (also known as SKU). The reporting through App Store Connect provides the SKU. The SKU are available in Summary Sales Report & Financial Report. Note: A SKU can represent the in-app purchase product that you offer in the app. Therefore, ensure that you provide the identifier of the product that you offer customers to purchase.

Hello - First, to answer the question you asked in the video: how is it possible for subscribers to change from one plan to another? We can see that you have set up one subscription group with ten different products - eight of which are currently Ready for Sale (active.) When a customer subscribes to any product, they can at any time switch to a different product in the same group as documented here. See attached screenshot specific to your app and its available products. If your app is not presenting upgrade/downgrade/crossgrade options, then customers are switching from their Manage Subscriptions page. Any changes from one subscription to another can only be completed by the customer. Developers must ensure that the ordering and grouping of individual subscription products within a subscription group is addressed to meet their business needs, as documented here, under the section titled Assign subscription levels. This setup is completed in App Store Connect. Ple

This is happening to our team as well. We had a build run overnight last night, stuck archiving. As well as several yesterday that ran for many hours (more than 2 hours) and had to be manually canceled. It was failing because the version string in our Info.plist was the same as an approved, Pending Developer Release version submitted on App Store Connect. We received (and missed) emails about this, until one of us noticed them this morning. Usually that sort of failure is reported in Xcode Cloud logs, and results in a failure of the job on-time. We should be refunded for the hours that the job spent idling, however applicable. Feedback assistant ticket: FB20279578

[quote='858495022, lucky06, /thread/799833?answerId=858495022#858495022, /profile/lucky06'] It seems that I should use OSSystemExtensionManager to start a System Extension … ? [/quote] Yes. Technically, this activates the system extension, which may or may not start it depending on the type of sysex. And, to be clear, you need this when you use system extension packaging, regardless of how you sign your extension. You can sign a sysex using: Apple Developerment, for day-to-day development Apple Developerment, for submission to the Mac App Store Developer ID Application, for direct distribution In all cases you need to use OSSystemExtensionManager. That’s correlated with the packaging, not with any specific signing identity. [quote='858495022, lucky06, /thread/799833?answerId=858495022#858495022, /profile/lucky06'] Could you share any other reference examples for OSSystemExtensionManager? [/quote] Sure. The Filtering Network Traffic sample code shows how to use OSSystemExtensionManager to act

Thank you. Setting preferredPlacement to fixed was the missing piece. I already had allowsHiding set to false and I’m not using any tab groups. The Edit button no longer appears in the sidebar. But I have discovered an iOS 26 (and iOS 18) bug in the process. I need to file a bug report but here’s the issue. I present the tab bar controller as a modal view controller on an iPad. If I resize the app window from full screen to a size that is horizontally compact while the tab bar controller is in view, the tab bar controller of course changes from showing a sidebar to showing an old style tab bar on the bottom with a More tab. Selecting the More tab now shows an Edit button. But only in this case. If the tab bar controller is presented after the app window is made horizontally compact, then the More tab does not show the Edit button.

Log Comparison Details for Bug Report Detailed Log Analysis: iOS 18.4 vs iOS 26 RC Complete Test Scenario Log Comparison Test Case: Type あ → Press Enter → Type あ → Delete → Type A iOS 18.4 / Xcode 16 (Correct Behavior) // Step 1: Type first あ === stringRange: 0[any]..<0[any], currentText: , replacementText: a changedText: a, allowChange: true === // Note: IME shows a first, then converts to あ // Step 2: IME converts a to あ === stringRange: 0[utf16]..<1[utf16], currentText: あ, replacementText: あ changedText: あ, allowChange: true === // Result: Text = あ, Count = 1 ✓ // Step 3: Press Enter (No additional delegate call - composition confirmed correctly) // Result: Text = あ, Count = 1 ✓ // Step 4: Delete あ === stringRange: 0[utf16]..<1[utf16], currentText: あ, replacementText: changedText: , allowChange: true === // Result: Text = , Count = 0 ✓ // Step 5: Type A === stringRange: 0[any]..<0[any], currentText: , replacementText: A changedText: A, allowChange: true === // Result: Text = A, Count = 1 ✓ Fina