Releases: superwall/Superwall-Android
Releases · superwall/Superwall-Android
1.1.0
Enhancements
- SW-2768: Adds
device.regionCode
anddevice.preferredRegionCode
, which returns theregionCode
of the locale. For example, if a locale isen_GB
, theregionCode
will beGB
. You can use this
in the filters of your campaign. - Adds support for unlimited products in a paywall.
- SW-2785: Adds internal feature flag to disable verbose events like
paywallResponseLoad_start
.
Fixes
- SW-2732: User attributes weren't being sent on app open until identify was called. Now they are
sent every time there's a new session. - SW-2733: Fixes issue where the spinner would still show on a paywall if a user had previously
purchased on it. - SW-2744: Fixes issue where using the back button to dismiss a paywall presented via
getPaywall
would calldidFinish
in thePaywallViewControllerDelegate
with the incorrect values. - Fixes issue where an invalid paywall background color would prevent the paywall from opening. If
this happens, it will now default to white. - SW-2748: Exposes
viewWillAppear
,viewDidAppear
,viewWillDisappear
andviewDidDisappear
methods ofPaywallViewController
which you must call when usinggetPaywall
. - Stops
Superwall.configure
from being called multiple times. getPresentationResult
now confirms assignments for holdouts.- Gracefully handles unknown local notification types if new ones are added in the future.
- SW-2761: Fixes issue where "other" responses in paywall surveys weren't showing in the dashboard.
1.0.3-beta.1
Fixes
- SW-2732: User attributes weren't being sent on app open until identify was called. Now they are
sent every time there's a new session. - SW-2733: Fixes issue where the spinner would still show on a paywall if a user had previously
purchased on it. - SW-2744: Fixes issue where using the back button to dismiss a paywall presented via
getPaywall
would calldidFinish
in thePaywallViewControllerDelegate
with the incorrect values. - Fixes issue where an invalid paywall background color would prevent the paywall from opening. If
this happens, it will now default to white. - SW-2748: Exposes
viewWillAppear
,viewDidAppear
,viewWillDisappear
andviewDidDisappear
methods ofPaywallViewController
which you must call when usinggetPaywall
.
1.0.2
1.0.1
Fixes
- Fixes serialization of
feature_gating
inSuperwallEvents
. - Changes the product loading so that if preloading is enabled, it makes one API request to get all products available in paywalls. This results in fewer API requests. It also adds retry logic on failure. If billing isn't available on device, the
onError
handler will be called when you try to present a paywall.
1.0.0
The SDK is no longer in alpha! For those upgrading from the previous alpha, here's what's changed:
Breaking Changes
- Changes the import path for the
LogScope
, andLogLevel
.
Fixes
- Fixes rare thread-safety crash when sending events back to Superwall's servers.
- Calls the
onError
presentation handler block when there's no activity to present a paywall on. - Fixes issue where the wrong product may be presented to purchase if a free trial had already been
used and you were letting Superwall handle purchases. - Fixes
IllegalStateException
on Samsung devices when letting Superwall handle purchases. - Keeps the text zoom of paywalls to 100% rather than respecting the accessibility settings text zoom,
which caused unexpected UI issues. - Fixes rare
UninitializedPropertyAccessException
crash caused by a threading issue. - Fixes crash when the user has disabled the Android System WebView.
1.0.0-alpha.45
Fixes
- Fixes issue where the
paywallProductsLoad_fail
event wasn't correctly being logged. This is a
"soft fail", meaning that even though it gets logged, your paywall will still show. The error message
with the event has been updated to include all product subscription IDs that are failing to be retrieved.
1.0.0-alpha.44
Fixes
- Fixes rare issue where paywall preloading was preventing paywalls from showing.
1.0.0-alpha.43
Enhancements
- Adds
handleLog
to theSuperwallDelegate
.
1.0.0-alpha.42
Fixes
- Makes sure client apps use our proguard file.
1.0.0-alpha.41
Fixes
- Removes need for
SCHEDULED_EXACT_ALARM
permission in manifest.