Skip to content

Releases: FlineDev/FreemiumKit

1.11.0

23 Oct 22:40
Compare
Choose a tag to compare
  • Adds support for dynamically controlling which tiers should be shown in the paywall by providing a showTierInPaywall closure. Learn More

1.10.2

23 Oct 15:12
Compare
Choose a tag to compare
  • Fixes an issue with redeem/restore buttons not fitting into screen on small iPhones. (#5)

1.10.1

12 Oct 13:45
Compare
Choose a tag to compare
  • Fixes a minor issue with the newly supported weekly subscription type.

1.10.0

12 Oct 12:11
Compare
Choose a tag to compare
  • Adds support for preselecting weekly subscription product type.

1.9.2

11 Oct 13:27
Compare
Choose a tag to compare

Products in paywalls are now more reliably sorted by their period length.

1.9.1

10 Oct 16:38
Compare
Choose a tag to compare
  • Fixes a bug inside the new legacyProductsIDsByTier logic which caused old purchases to not get properly detected.
  • Fixes a bug that the paywall didn't auto-close upon successful restoring of a purchase.

1.9.0

08 Oct 11:49
Compare
Choose a tag to compare

Adds a new legacyProductsIDsByTier parameter you can set on FreemiumKit.shared upon app start if you have legacy products on App Store Connect that are no longer part of your paywall, to maintain access for existing customers. This is only needed if you historically had a different set of subscriptions/lifetime purchases and created new ones at a later time. If all your products you ever released are currently on your paywall, you don't need this.

1.8.0

07 Oct 22:53
Compare
Choose a tag to compare
  • Adds optional onAppear and onDisappear parameters to .paywall(isPresented:) modifier.
  • Adds optional onPaywallAppear and onPaywallDisappear parameters to PaidStatusView, PaisFeatureButton, and PaidFeatureView.

1.7.3

26 Sep 09:55
Compare
Choose a tag to compare

Identical to 1.7.2 – re-released to avoid Git/SwiftPM caching issues in some rare cases (due to force-pushed commit).

1.7.2

25 Sep 12:29
Compare
Choose a tag to compare
  • Fixes an issue with the privacy manifest missing some fields, causing the generated privacy report to show warnings.