This investigation started with a question: someone in the family has bought Flick Pro Lifetime, so why does another member still see the paywall? If that member is a child, could parental approval or device restrictions affect access?
We followed the purchase, restore, startup and foreground paths through the code. We found a startup ordering problem and two gaps in the family purchase experience.
First, has Apple provided an entitlement?
Being eligible to share, waiting for parental approval and having an unfinished redemption are different from holding a valid purchase entitlement. An app should unlock from the transactions Apple provides. A message offering a free acquisition does not, by itself, prove that a purchase is complete. Downloading the app for free also does not establish access to the separate non-consumable Pro purchase.
We first inspected Transaction.currentEntitlements. Flick already read this sequence and checked verification, the product ID and revocation. It did not filter for ownershipType == .purchased, so .familyShared already granted access. The product ID is me.mahui.app.Flick.pro.lifetime.
Restore Purchase already called AppStore.sync() and then refreshed entitlements. Apple explains that some shared non-consumable purchases require a family member to restore them. The sync call should follow an explicit tap on Restore Purchase, rather than automatically prompting for authentication at startup. See Supporting Family Sharing and AppStore.sync().
The issue we reproduced: prices delayed the first entitlement check
The original initialization task fetched the product name and price before checking existing access:
Task {
await loadProduct()
await refreshEntitlements()
}
This made two separate jobs depend on one another. While the product request had not returned, the initial entitlement check could not start, and isPurchased kept its default value of false. That wait affected both personal purchases and Family Sharing.
A separate refresh when the app became active could mask the issue, but startup access should not depend on that lifecycle notification. We now start the jobs independently:
Task { await refreshEntitlements() }
Task { await loadProduct() }
The fix does not depend on which task runs first. Existing access no longer waits for the price request to finish. In the simulated regression, we held the product request open: the old startup path made zero entitlement reads, while the corrected code unlocked a valid shared entitlement with the price still unavailable. The old code would continue refreshing after a product error returned; the defect was the delay while that request remained pending.
For child accounts, separate approval from blocked purchases
Ask to Buy uses StoreKit’s pending purchase flow. When Flick receives .pending, it leaves Pro locked, clears the purchase spinner and explains that parental approval or another verification step may be needed. If the purchase completes, a verified transaction arrives through Transaction.updates and access is refreshed.
A declined request does not produce a completed transaction. The app therefore stays locked and cannot claim to know that a parent declined it. We do not persist a pending flag that permanently disables purchasing, which could prevent another attempt after a declined request. See Apple’s Ask to Buy testing guidance.
Screen Time and device management can separately block new purchases. We added AppStore.canMakePayments checks: the paywall replaces the new-purchase button with an explanation, and the purchase method checks the system again in case restrictions changed while the page was open.
Blocking new purchases does not turn off existing personal or shared access. Entitlement reads continue, and Restore Purchase remains available. This flag is not an age check; device management can also make it false. See canMakePayments.
A restore message must make sense to family members
The old empty-result message asked people to sign in with the account used for the purchase. That can make sense for a personal purchase, but might lead a family member to think they should sign in to a parent’s account on a child’s device.
The message now distinguishes the two paths. Personal purchasers should check the Apple Account used for Media & Purchases. Family members should confirm that someone purchased Pro and check their family’s Purchase Sharing settings, using their own family account. An empty restore result does not prove that nobody in the family ever purchased Pro.
The local Products.storekit value familyShareable: true only describes the development configuration. It does not prove that sharing is enabled for the live in-app purchase. The live setting, each member’s purchase account, sharing preferences and transaction delivery still need checking. See Apple’s shared purchase troubleshooting.
What we verified, and what remains
- 25 simulated transaction checks passed. They compile the actual purchase code against a StoreKit test double, covering stalled, failed and empty product requests, shared and personal access, verification, revocation, restore, changing purchase restrictions and approval-state handling. These test the app’s control flow.
- iOS Simulator and Mac Catalyst Debug builds passed, as did the five-language string checks. Compilation does not establish a completed purchase with Apple’s service.
- Native StoreKit Testing did not complete. We prepared four tests. Both test projects compiled, but the local simulator/XCTest runs did not finish; a bounded retry was interrupted after timing out. We obtained no complete assertion results and did not classify this as a purchase-code assertion failure.
- Real accounts and production configuration remain unverified. This includes adult and child family members, cross-device and purchase-account changes, reopening after a pending approval, Apple’s delivery of shared and revoked transactions, and the live App Store Connect configuration.
The code changes address the reproduced startup wait and add purchase restriction handling and clearer family restore guidance. Publishing this article makes the engineering record public. It does not mean that an app update has shipped or that real family-account testing is complete.
If Pro is still locked for you
Start with Restore Purchase on Flick’s paywall. For Family Sharing, check your own family account, Media & Purchases and Purchase Sharing. If approval or redemption is still pending, complete Apple’s system flow first. If access is still missing, contact Flick support with your app and system versions, whether access comes from a personal purchase or Family Sharing, and the restore message you see.