{"id":42710,"date":"2024-04-01T15:17:33","date_gmt":"2024-04-01T19:17:33","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=42710"},"modified":"2024-04-01T15:17:33","modified_gmt":"2024-04-01T19:17:33","slug":"app-store-subscriptions-and-family-sharing","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2024\/04\/01\/app-store-subscriptions-and-family-sharing\/","title":{"rendered":"App Store Subscriptions and Family Sharing"},"content":{"rendered":"

Craig Hockenberry<\/a>:<\/p>\n

Your code and the App Store don’t agree about when a subscription expired. The cause of this is Apple’s StoreKit sample code<\/a>. It’s likely that you have some code similar to line 246 of Store.swift<\/code>:<\/p>

subscriptionGroupStatus = try<\/strong>? await<\/strong> subscriptions.first?.subscription?.status.first?.state<\/pre>
That code will work fine until you encounter a customer that has Family Sharing enabled, as most do. The issue is that the Product.SubscriptionInfo<\/code> can contain multiple items, and the code above only checks the first one. <\/p>
How can that happen? With Family Sharing, the people who are using the subscription act independently: one may subscribe for a year and then cancel. Then another could subscribe at a later date for only a month. You have to check all of the subscriptions, not just the first one.<\/p><\/blockquote>\n
As he notes, it’s not documented that the sample code doesn’t support Family Sharing. And, even if you’re aware of this issue, there’s no reasonable way to test your code in Xcode, TestFlight, or even production.<\/p>\n
Previously:<\/p>\n