Skip to content

5.4.2

Latest
Latest

Choose a tag to compare

View all tags
@El-Fitz El-Fitz released this 03 Oct 15:15
5.4.2
058adc3
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Purchasely SDK – Version 5.4.2

We're excited to share version 5.4.2, which introduces important updates, new features, and several improvements to stability and UI. Please read carefully, as this version includes a breaking change.

⚠️ Important Notice regarding iOS SDK Versions 5.4.0 and 5.4.1
We have identified an important issue in versions 5.4.0 and 5.4.1 on iOS devices, affecting all Screens that use vertical pickers or buttons with texts per row = 2. As a result, this version has been removed and must not be used.
If you are currently using 5.4.0 or 5.4.1, please update immediately to version 5.4.2, which resolves the issue.

🚨 Breaking Change

  • Renamed logging level enum

    • 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.

    • Example before/after:

      // Before
logLevel: PLYLogger.logLevel = .error

// Now
logLevel: PLYLogger.PLYLogLevel = .error

✨ New Features

  • 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.
    • Documentation and integration details are available in our updated privacy guide.

  • Safe Areas Handling

    • You can now choose whether Purchasely screens should respect the system's safe areas (e.g. notch, home indicator, or system bars).
    • This provides greater flexibility for developers who want tighter control over screen layout and presentation.

🛠 Fixes & Improvements

  • Events

    • Fixed several issues where certain events or their properties were not being tracked consistently.

  • Flows

    • Fixed UI glitches that could occur in certain Flow configurations.
    • Improved screen transitions, navigation consistency, and dismissal logic within Flows.

  • General optimizations

    • Updated method visibility: several methods have been made public to ensure compatibility and usage within the hybrid bridges.
    • Minor performance improvements and codebase refinements to ensure smoother integration and runtime stability.

⚡️ Upgrade Notes

  • Make sure to update your logging configuration to use PLYLogLevel.
  • Review the new privacy-level APIs if GDPR compliance is part of your workflow.
Assets 5
Loading