Files
damus/damus/Models/Purple/PurpleStoreKitManager.swift
Daniel D’Aquino 4a4a58c7b5 iap: handle login and logout
This commit adapts the functionality around login/logout with relation
to Damus Purple In-App purchases (IAP). Due to (apparent) limitations on
Renewable subscription In-app purchases (It seems that there can only be
one active IAP subscription per device or Apple ID), these changes add
support for only one IAP subscription at a time.

To prevent confusion, a customer who logs out and logs into a separate
account will see a message indicating the limitation. Any other Nostr
account won't be able to manage IAP on a device that contains an IAP
registered to a different user.

To make this feature possible, the following changes were made to the
code:

1. IAP purchases are now associated with an account UUID. This account
   UUID is generated by the server. Each npub gets one and only one UUID
   for this purpose.

2. This UUID is used to determine which npub owns the IAP on the device.
   It is used as the source of truth when determining whether a
   particular Purple account is manageable on a device or not

3. `DamusPurple` was changed to adhere to a new IAP flow API design
   changes. Previously, the client would create an (inactive) account,
   and then send the IAP receipt to the server for activation. Now, the
   client fetches the npub's UUID from the server, associates it with an
   IAP during purchase, and sends the IAP receipt to the server. The
   server will then bump the expiry (if it's a renewal) or create a new
   active account (if it's the first time).

4. Several changes were made to the StoreKit handling code to improve
   handling:

  a. The `DamusPurple.StoreKitManager` class now records all purchased
     product updates, and sends them to the delegate each time the
     delegate is updated. This helps ensure we do not miss purchased
     product updates regardless of when and if `DamusPurpleView` is ever
     instantiated.

  b. `DamusPurple.StoreKitManager` is now used by `DamusPurple` in a
     singleton pattern via `DamusPurple.StoreKitManager.standard`. This
     helps maintain the local purchase history consistent (and avoid
     losing such data) after `DamusState` or its `DamusPurple` are
     destroyed and re-initialized.

  c. Added logs (using the logger) to help us debug/troubleshoot
     problems in the future

5. Changed the views around DamusPurple, to only show IAP
   purchase/management options if applicable to a particular account. It
   also shows instructive messages in other scenarios.

Testing
-------

damus: This commit
damus-api: d3956ee004a358a39c8570fdbd481d2f5f6f94ab
Device: iPhone 15 simulator
iOS: 17.2
Setup:

- Xcode (local) StoreKit environment
- All StoreKit transactions deleted before starting
- Running `damus` app target (which contains test StoreKit products)

- Local damus-api server running with `npm run dev` and
  `MOCK_VERIFY=true` to disable real receipt verification

- Damus setup with experimental IAP support enabled, and Purple
  environment set to "Test (local)" (localhost)

- Two `nsecs` readily available for account switching
- Clean DB (Delete db files before starting)

Steps:
1. Open the app and sign in to the first account

2. Go to Damus Purple screen. Marketing screen with buttons to purchase
   products should be visible. PASS

3. Buy a product and monitor server logs as well as the screen.
  a. IAP confirmation dialog should appear. PASS

  b. After confirmation, server logs should show a receipt was sent
     IMMEDIATELY and the response should be an HTTP 200. PASS

  c. The welcome and onboarding screens should appear as normal. PASS

  d. Once the onboarding sheet goes away, the Purple screen should now
     show the account information. PASS

  e. The account information should be correct. PASS

  f. Under the account information, there should be a "manage" button. PASS

4. Click on "manage" and verify that the iOS subscription management
   screen appears. PASS

5. Now log out and sign in to the second account

6. Go to Damus Purple screen.
  a. Marketing screen should be visible. PASS

  b. There should be no purchase buttons. instead, there should be a
     message indicating that there can only be one active subscription
     at a time, and that the app is unable to manage subscription for
     this second acocunt. PASS

7. Log out and sign in to the first account. Go to the Purple screen.
  a. Account info with the manage button should be visible like before. PASS

8. Through Xcode, delete transactions, and restart the app. This will
   simulate the case where the user bought the subscription externally.

9. Go to the Purple screen.
  a. Account info should be visible and correct. PASS
  b. Below the account info, there should be a small note telling the
     user to visit the website to manage their billing. PASS

Closes: https://github.com/damus-io/damus/issues/1815
Signed-off-by: Daniel D’Aquino <daniel@daquino.me>
Reviewed-by: William Casarin <jb55@jb55.com>
Signed-off-by: William Casarin <jb55@jb55.com>
2024-02-19 10:38:59 -08:00

131 lines
6.0 KiB
Swift
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
//
// PurpleStoreKitManager.swift
// damus
//
// Created by Daniel DAquino on 2024-02-09.
//
import Foundation
import StoreKit
extension DamusPurple {
class StoreKitManager { // Has to be a class to get around Swift-imposed limitations of mutations on concurrently executing code associated with the purchase update monitoring task.
// The delegate is any object that wants to be notified of successful purchases. (e.g. A view that needs to update its UI)
var delegate: DamusPurpleStoreKitManagerDelegate? = nil {
didSet {
// Whenever the delegate is set, send it all recorded transactions to make sure it's up to date.
Task {
Log.info("Delegate changed. Try sending all recorded valid product transactions", for: .damus_purple)
guard let new_delegate = delegate else {
Log.info("Delegate is nil. Cannot send recorded product transactions", for: .damus_purple)
return
}
Log.info("Sending all %d recorded valid product transactions", for: .damus_purple, self.recorded_purchased_products.count)
for purchased_product in self.recorded_purchased_products {
new_delegate.product_was_purchased(product: purchased_product)
Log.info("Sent StoreKit tx to delegate", for: .damus_purple)
}
}
}
}
// Keep track of all recorded purchases so that we can send them to the delegate when it's set (whenever it's set)
var recorded_purchased_products: [PurchasedProduct] = []
// Helper struct to keep track of a purchased product and its transaction
struct PurchasedProduct {
let tx: StoreKit.Transaction
let product: Product
}
// Singleton instance of StoreKitManager. To avoid losing purchase updates, there should only be one instance of StoreKitManager on the app.
static let standard = StoreKitManager()
init() {
Log.info("Initiliazing StoreKitManager", for: .damus_purple)
self.start()
}
func start() {
Task {
try await monitor_updates()
}
}
func get_products() async throws -> [Product] {
return try await Product.products(for: DamusPurpleType.allCases.map({ $0.rawValue }))
}
// Use this function to manually and immediately record a purchased product update
func record_purchased_product(_ purchased_product: PurchasedProduct) {
self.recorded_purchased_products.append(purchased_product)
self.delegate?.product_was_purchased(product: purchased_product)
}
// This function starts a task that monitors StoreKit updates and sends them to the delegate.
// This function will run indefinitely (It should never return), so it is important to run this as a background task.
private func monitor_updates() async throws {
Log.info("Monitoring StoreKit updates", for: .damus_purple)
// StoreKit.Transaction.updates is an async stream that emits updates whenever a purchase is verified.
for await update in StoreKit.Transaction.updates {
switch update {
case .verified(let tx):
let products = try await self.get_products()
let prod = products.filter({ prod in tx.productID == prod.id }).first
if let prod,
let expiration = tx.expirationDate,
Date.now < expiration
{
Log.info("Received valid transaction update from StoreKit", for: .damus_purple)
let purchased_product = PurchasedProduct(tx: tx, product: prod)
self.recorded_purchased_products.append(purchased_product)
self.delegate?.product_was_purchased(product: purchased_product)
Log.info("Sent tx to delegate (if exists)", for: .damus_purple)
}
case .unverified:
continue
}
}
}
// Use this function to complete a StoreKit purchase
// Specify the product and the app account token (UUID) to complete the purchase
// The account token is used to associate with the user's account on the server.
func purchase(product: Product, id: UUID) async throws -> Product.PurchaseResult {
return try await product.purchase(options: [.appAccountToken(id)])
}
}
}
extension DamusPurple.StoreKitManager {
// This helper struct is used to encapsulate StoreKit products, metadata, and supplement with additional information
enum DamusPurpleType: String, CaseIterable {
case yearly = "purpleyearly"
case monthly = "purple"
func non_discounted_price(product: Product) -> String? {
switch self {
case .yearly:
return (product.price * 1.1984569224).formatted(product.priceFormatStyle)
case .monthly:
return nil
}
}
func label() -> String {
switch self {
case .yearly:
return NSLocalizedString("Annually", comment: "Annual renewal of purple subscription")
case .monthly:
return NSLocalizedString("Monthly", comment: "Monthly renewal of purple subscription")
}
}
}
}
// This protocol is used to describe the delegate of the StoreKitManager, which will receive updates.
protocol DamusPurpleStoreKitManagerDelegate {
func product_was_purchased(product: DamusPurple.StoreKitManager.PurchasedProduct)
}