3.7.2

What's new

• Fix of NSInvalidArgumentException while trying to parse nil as Json on iOS.

4.0.0

New major release of Qonversion Unity SDK

For the list of changes and migration guide, please, visit the documentation.

3.7.1

What's new

• Fixed an issue causing automation event losses on Android.
• Fixed a rare issue with the permissions cache on Android.

3.7.0

What's new

• Added a Source property to the Permission object - use it to know where this permission is originally from - App Store, Play Store, Stripe, etc.
• Added a method getNotificationCustomPayload to get the extra data you've added to automation notifications.
• Purchase tracking error handling improved to guarantee delivery.

3.6.2

What's new

• Added a new user property AppSetId - a unique user identifier for all the developer's applications on Android. May be used for some integrations.

3.6.1

What's new

• Fixed required offeringId bug for purchaseProduct call on iOS.

3.6.0

What's new

• Big refactoring of the native modules made to simplify further upgrades and make it easy to keep the SDK functionality up-to-date.

3.5.1

What's new

• C# 8.0 support (for Unity 2020.3 and below)

3.5.0

What's new

• Added support of network connection lack or unexpected backend errors. Now Qonversion SDK will handle user permissions correctly even if it can't reach out to the API and will actualize them with the next successful request. Also, products and offerings become permanently available after the first successful launch - nothing will interfere user from the purchase.
• Added method setPermissionsCacheLifetime to configure the lifetime of permissions cache. It is used if we faced any error trying to get permissions from our API. Defaults to one month.
• Added a new defined property FirebaseAppInstanceId for Firebase integration.
• (Android only) Fixed a bug with introductory price tracking causing wrong data in the analytics dashboard for some purchases.

3.4.4

What's new

• Added isCancelled flag to purchase result. You can now check if the error occurred because the user manually canceled the flow or not. To receive that flag start using Purchase, PurchaseProduct, UpdatePurchase, and UpdatePurchaseWithProduct methods with new OnPurchaseResultReceived delegate instead of deprecated ones with OnPermissionsReceived delegate.
• Added multiple parallel requests support for CheckPermissions, Restore, Products, and Offerings methods. If you were calling these methods from different parts of your app at the same moment, the first call used not to be responded at all. Now everything works fine!