Share PaywallPromoOfferCache between main and exit offer paywalls

[facumenzella]

Summary

• Fixes a race condition where promotional offers were not applied when purchasing quickly from exit offer paywalls
• The exit offer paywall was creating a new PaywallPromoOfferCache instance, causing eligibility to be computed asynchronously
• If a user purchased before the computation completed, the promotional offer ID wouldn't be included in the purchase

Changes

• Add promoOfferCache property to PaywallViewConfiguration
• Update PaywallsV2View to accept an optional external cache (creates new one if not provided)
• Share cache through SwiftUI modifiers (PresentingPaywallModifier, PresentingPaywallBindingModifier)
• Share cache through UIKit path (PaywallViewController for hybrid SDKs)
• Use internal init(content:) for exit offer creation to pass the shared cache

How It Works

1. Main paywall creates PaywallPromoOfferCache and computes eligibility
2. When exit offer is shown, it receives the same cache instance
3. Exit offer's .task still calls computeEligibility() (for any new products)
4. For already-computed products, get() returns immediately with the cached promotional offer

Test plan

• Verify promotional offers work on main paywall (no regression)
• Verify promotional offers work on exit offer paywall when purchasing quickly
• Test SwiftUI path with presentPaywallIfNeeded
• Test UIKit path with PaywallViewController
• Test hybrid SDKs (React Native, Flutter) if applicable

🤖 Generated with Claude Code

[claude]

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

[emerge-tools]

📸 Snapshot Test

242 unchanged

Name	Added	Removed	Modified	Renamed	Unchanged	Errored	Approval
RevenueCat com.revenuecat.PaywallsTester	0	0	0	0	242	0	N/A

---

🛸 Powered by Emerge Tools