I'm looking for the latest advice on detecting customers who have bought my app prior to its conversion to freemium, so I can offer them a free period. This seems like a pretty common thing to want to do. I'm adding a range of subscriptions to a previously "paid" app, and don't want to annoy customers who have recently bought it outright. Over the last decade there has been a great deal of confusing advice posted on this subject, so does anyone know the best way to tackle this when supporting Sonoma and later? I'm currently implementing the new subscription solution based around SubscriptionStoreView. I don't have a server to support my app as it isn't cost-effective for my situation, and much of the Apple video content seems centred around having one. Is it possible to do the receipt checking and detection of original paid purchase date in-app? Maybe using StoreKit2? Can I do this with introductory offers? Any help greatly appreciated. UPDATE: I've just started re-watching the WWDC 2022 Video "What's new with in-app purchase" and it seems that AppTransaction is the way to go. Any thoughts on this?

I'm offering a free trial period for each of four auto-renewable subscriptions. Does anyone know the best way to detect whether a customer is still in the trial period, and to calculate the remaining trial days? I'm using Storekit 2. I've seen vague answers about using the Transaction purchaseDate and expiry date, but the documentation is incredibly vage as to what those values actually represent when it comes to a free trial period. What does purchase Date actually mean when you're in a free trial? Any help greatly appreciated.

This is a copy of a reply to this post. https://developer.apple.com/forums/thread/722222?page=1 I'm posting as new in the hope someone might have more up-to-date information, as I'm pulling out what little hair I have left. I'm using Storekit 2, testing in Xcode with a local Storekit config file. I have created a very minimal system to investigate this issue. I have a SwiftUI-based window using SubscriptionStoreView, and my app set up with the usual listener. I have four types of auto renewing subscription, configured in the local Storekit config file. With my app running, I subscribe to the lowest-level subscription I offer, via the SubscriptionStoreView. Notification of the inital purchase arrives, but subsequent auto-renewals do not trigger any action in my listener for Transaction.updates. They arrive as expected in the Transaction Manager. Radio silence in my listener. If I upgrade one subscription (via my SubscriptionStoreView) I see this reflected in the UI immediately, and also in the Transaction Manager, but the update that arrives in Transaction.updates refers to the old subscription, and has the isUpgraded flag set to false. Also, can anyone remind me what the grey warning triangle next to entries in the Transaction Manager means. I'm assuming it means unfinished, as that's what the sidebar indicates. Can the testing system really be this broken, or am I wildly off the mark? Unless I'm doing something fundamentally wrong this all seems extremely flakey, but happy to be proved wrong. I find this all rather unsettling if I can't test reliably, and am concerned that I my app may end up in this situation if I use storekit 2: https://stackoverflow.com/questions/73530849/storekit-renewal-transactions-missing-in-transaction-all-or-transaction-updates

I currently have a paid app in the Mac App Store and am about to release a freemium version - free with three auto-renewing subscriptions. Is there a way to set things up in App Store Connect such that this next release of my app becomes free at the point when it goes live? I need to synchronise the changeover. I've read posts suggesting you just set the price to zero, but that doesn't synchronise the change (as far as I can tell). Thanks in advance. UPDATE: I see you can schedule a price change. Is the answer to not auto-release the app when it's approved, and to then coordinate its release date with the scheduled price change?