All Versions
56
Latest Version
Avg Release Cycle
82 days
Latest Release
-

Changelog History
Page 4

  • v3.3.3 Changes

    ๐Ÿ› Bug Fixes

    • ๐Ÿ›  Fix an issue where rapidly showing and hiding messages could result in messages becoming orphaned on-screen.
  • v3.3.2 Changes

    ๐Ÿ‘Œ Improvements

    • MessageView is smarter about including additional accessibility views for cases where you've added accessible elements to the view. Previously only the button was included. Now all views where isAccessibilityElement == true.

      Note that all nib files now have isAccessibilityElement == false for titleLabel, bodyLabel and iconLabel (titleLabel and bodyLabel are read out as part of the overall message view's text). If any of these need to be directly accessible, then copy the nib file into your project and select "Enabled" in the Accessibility section of the Identity Inspector.

  • v3.3.1 Changes

    ๐Ÿ› Bug Fixes

    • ๐Ÿ›  Fix regression where the UI was being blocked when using DimMode.none.
  • v3.3.0 Changes

    ๐Ÿ”‹ Features

    • โž• Add proper support for VoiceOver. See the [Accessibility section](README.md#accessibility) of the readme.
  • v3.2.1 Changes

    ๐Ÿ› Bug Fixes

    • ๐Ÿ›  Fix infinite loop bug introduced in 3.2.0.
  • v3.2.0 Changes

    ๐Ÿ”‹ Features

    • โž• Added the ability to display messages for an indefinite duration while enforcing a minimum duration using Duration.indefinite(delay:minimum).

    This option is useful for displaying a message when a process is taking too long but you don't want to display the message if the process completes in a reasonable amount of time.

    For example, if a URL load is expected to complete in 2 seconds, you may use the value unknown(delay: 2, minimum 1) to ensure that the message will not be displayed most of the time, but will be displayed for at least 1 second if the operation takes longer than 2 seconds. By specifying a minimum duration, you can avoid hiding the message too fast if the operation finishes right after the delay interval.

    ๐Ÿ› Bug Fixes

    • Prevent views below the dim view from receiving accessibility focus.
    • Prevent taps in the message view from hiding when using interactive dim mode.
    • ๐Ÿ›  Fix memory leak of single message view
  • v3.1.5 Changes

    ๐Ÿ› Bug Fixes

    • ๐Ÿ›  Fix memory leak of MessageViews.
  • v3.1.4 Changes

    ๐Ÿ› Bug Fixes

    • ๐Ÿ›  Fixed an issue where UIKit components were being instantiated off the main queue.
  • v3.1.3 Changes

    ๐Ÿ”‹ Features

    • โž• Added the ability to set a custom value on MessageView.id. This can be useful for dismissing specific messages using a pre-defined id.
  • v3.1.2 Changes

    ๐Ÿ”‹ Features

    • ๐Ÿ”„ Changed the default behavior when a message is displayed in its own window (such as with .window presentation context) to no longer become the key window in order to prevent the keyboard from dismissing. If one needs the message's window to become key, this can be done by setting SwiftMessages.Config.becomeKeyWindow to true. See

    ๐Ÿ› Bug Fixes

    • ๐Ÿ”„ Changed the internal logic of hiding a message view to always succeed to work around the problem of the hide animation failing, such as when started while the app is not active.
    • ๐Ÿ‘Œ Improved reliability of the automatic adjustments made to avoid message views overlapping the status bar, particularly when using the .view presentation context.