All Versions
56
Latest Version
Avg Release Cycle
82 days
Latest Release
-
Changelog History
Page 1
Changelog History
Page 1
-
v9.0.6 Changes
๐ Features
- โ Add
UIView
associated type toEvent
, e.g.willShow(UIView)
so that event listeners can inspect the view. - โ Add
Event.id: String?
property so that event listeners can reason about the view's ID.
- โ Add
-
v9.0.5 Changes
๐ Fixes
- #482 Fix timing of
KeyboardTrackingView
callbacks. - ๐ #483 KeyboardTrackingView causes a small space under bottom-style view
- #482 Fix timing of
-
v9.0.4 Changes
- #471 Xcode 13 issue - Enum cases with associated values cannot be marked potentially unavailable with '@available'
- ๐ Improve colors for dark mode.
-
v9.0.3 Changes
๐ Fixes
- #467 Lower or equal level window's views disappear upon hide
- #466 Alert not shown after Biometry check
- ๐ #465 Fix broken Carthage build. The Carthage build was broken due to the
iMessageDemo
project's use of CocoaPods and the automatically generatedSwiftMessages
framework scheme created by CocoaPods. The podfile was modified to delete this scheme, but Carthage users may need to runpod install
on theiMessagesDemo
project, if they have CocoaPods installed, or manually delete theiMessageDemo/Pods/Pods.xcodeproj/xcuserdata
folder.
-
v9.0.2 Changes
๐ Fixes
- ๐ Fix app extension compile error when using CocoaPods.
-
v9.0.1 Changes
๐ Fixes
- โช #455 #458 Restore key window after message is interacted with. When a message becomes the key window, such as if the user interacts with the message, iOS does not automatically restore the previous key window when the message is dismissed. SwiftMessages has some logic in
WindowViewController
to restore the key window. This change makes that logic more robust.
- โช #455 #458 Restore key window after message is interacted with. When a message becomes the key window, such as if the user interacts with the message, iOS does not automatically restore the previous key window when the message is dismissed. SwiftMessages has some logic in
-
v9.0.0 Changes
๐ Features
- #447 Add the ability to show view controller in a new window with
SwiftMessagesSegue
. This capability is available when usingSwiftMessagesSegue
programmatically by supplying an instance ofWindowViewController
as the segue's source view controller.
๐ Changes
- ๐ This release has minor breaking changes in the
WindowViewController
initializers. ThewindowLevel
is no longer accepted as an argument because theconfig
parameter should specify the window level in thepresentationContext
property.
๐ Fixes
- #451 Fix app extension crash
- #447 Add the ability to show view controller in a new window with
-
v8.0.5 Changes
๐ Fixes
- โช #446 Restore previous key window on dismissal if the message assumed key window status.
-
v8.0.4 Changes
๐ Features
- #442 Add
MarginAdjustable.respectSafeArea
option to exclude safe area from layout margins. - ๐ #430 Support disable
becomeKeyWindow
from SwiftMessages.Config. This is a workaround for potential issues with apps that display additional windows.
๐ Fixes
- โช #437 Revert to explicitly specifying "SwiftMessages" as the module in nib files.
- #440 Fix crash when using SwiftMessages in app extension
- #442 Add
-
v8.0.3 Changes
October 25, 2020