missing package product

We used to get this error, cause our products are set up in Monetization/In-App Purchase section, specifically non-consumable. We then switched to set up products in Monetization/non-

We used to get this error, cause our products are set up in Monetization/In-App Purchases section, specifically non-consumable. We then switched to set up products in Monetization/Subscriptions: Non-Renewing Subscriptions. We no more got errors about: An In-App Purchase has been returned. Hope this could help someone in the future. Best luck in building your dream chaps!

(Reordering questions for clarity...) Questions: Is this behavior intentionally blocked by iOS as a user privacy/power decision? So, in general, the normal behavior of iOS is that it does not relaunch applications that have been force quit by the user, primarily to simplify the user’s general management of background app usage. However... Is it officially supported for iBeacon region monitoring to relaunch an app after the user force-quits it? ...there are exceptions and, yes, region monitoring is one of them. The issue here is that there are use cases we want to support that don't really work within the standard force quit behavior. The canonical example here is supporting airline apps notifying the user when they arrive at the airport, as it isn't really reasonable to expect the user to have not force quit an app they may not have used for weeks or even months. Are there any supported mechanisms to resume beacon monitoring after a force-quit? Not specifically, no. The main issue here is that your app needs

It's really bad, we pay for the Developer account (1), then pay again on anything we sell (2) and then again if we advertise in App store (3) and then lose money further when they don't approve apps on time (4) --- Incredibly one-sided. Our app has been In Review for 7+ days. We resubmitted to make sure everything was fine, and once again, one initial reply 4 days ago for which we replied right away, and we are still stuck in In Review. We've done expedited requests, 3 support tickets, explained there are critical bugs that need to go through (not to mention clients that expect it live) --- nothing --- no reply whatsoever. It used to be that Android was like this before, but now the service quality is the exact opposite. Not to mention, this is not a new app; we've released monthly for the past 5 years and have thousands of positive reviews. It's as if our entire business is at a standstill, and worse yet, declining due to gate-keeping.

Hello - It looks like the one piece missing from your setup is a localization for the Subscription Group itself. Please add at least one localization for the Subscription Group, as documented here in the section towards bottom of page called Add localization. Once a Subscription Group localization is added, your subscription In-App Purchase should be ready to submit to App Review. Please let us know if you need any further assistance. Thank you.

What I just forgot: In the FB ticket I mentioned the Apple ID of my productive app, so you could just run the app under Sequoia and Tahoe ... unfortunately it is way too complex to act as a sample app (that's why I was additionally providing the minimal app with a less dramatic result)...

Hi Albert, Thanks for your swift reply! I had used Instruments to analyze the app's memory allocations and releases without identifying any significant memory leak (under macOS 26). I'm happy to dive deeper supply an Instrument trace in the corresponding ticket, these days. On the macOS 15 virtual machine, Xcode / Instruments is not installed, but honestly I expect other developers to have similar observations, and I'm not talking about some minor increase, but (in my productive app) by five times... Regarding the mentioned consumption by Thumbnail - which was way beyond any justified memory allocation: I could neither reproduce the customer's issue, nor debug / analyze app's Preview / Thumbnail extensions (actually I filed a corresponding DTS ticket): Without qlmanage to work for modern extensions, Xcode is not properly attaching the running extension to the Finder - or is just me, missing some concrete instructions (what I asked for in the DTS request). Don't get me wrong, I'm willing to p