5.4

Purchasely SDK 5.4.0 introduces two new features:

• GDPR & Privacy Levels
• Safe Areas Handling

Version per platform

Changelog per platform is available on their GitHub repositories.
You can access them by clicking on the version number.

🚨 Breaking change: iOS Logging Level Renamed

On iOS, PLYLogger.logLevel has been renamed to PLYLogLevel.

If you are currently configuring the logging level in your project, you will need to update your references accordingly.

// Before  
logLevel: PLYLogger.logLevel = .error

// Now  
logLevel: PLYLogger.PLYLogLevel = .error

📱 Android Target SDK

The SDK now targets API 35, ensuring compliance with the latest Google rules and guidelines.

💳 Google Billing v8 Compatibility

While the SDK continues to use Google Billing v7.1.1, it is now fully compatible with version 8.

🔐 GDPR & Privacy Levels

The SDK now offers built-in support for handling privacy levels.
This enables developers to adapt their user experience to different GDPR requirements and to better manage user consent directly within Purchasely.

📐 Safe Areas Handling

Starting from the v5.4.0, you can choose whether Purchasely screens should respect the system’s safe areas (e.g. status bar, navigation bar).
This provides greater flexibility for developers who want tighter control over screen layout and presentation.

🛠 Fixes & Improvements

iOS

• Fixed several issues where certain events or their properties were not being tracked consistently.
• Fixed UI glitches that could occur in certain Flow configurations.
• Improved screen transitions, navigation consistency, and dismissal logic within Flows.
• Minor performance improvements and refinements to ensure smoother integration and runtime stability.

Android

• When intercepting a close action, you can now use PLYCloseReason enum to identify whether it was triggered by the close button or a system back gesture.
• Fixed a bug where cached presentations with placement IDs were not being properly invalidated.
• Enhanced deeplinks handling and presentations display.
• Fixed an Out of Memory issue in the DiagnosticManager.
• Minor performance improvements and codebase refinements to ensure smoother integration and runtime stability.