Closed giofid closed 3 years ago
If you are using the global SwiftMessages instance, your first message will block the queue until you dismiss it. SwiftMessages does not attempt to detect when a message should be dismissed sooner than the timing you specified.
You have a couple of options:
SwiftMessages
so that the queue is local to the view controller.Hope that helps.
Ok. I will use option 2. It seems the most clean one.
Thank you Timothy.
Hi @wtmoose, I try to briefly describe a potential problem found in the library. I have a view controller
V1
that presents (modally) a view controllerV2
, andV2
shows a swifty-message with duration set to.forever
. IfV2
is dismissed and presented again, when it tries to show again the same swifty-message, nothing appears.I attach a sample project: SMExample.zip
As a workaround (honestly, it looks like an ugly workaround), I have to call
hide(animated:)
before to show the swifty-message and I have to callshow(config:, view:)
intoDispatchQueue.main.async
.I don't know if this problem is related to this one: #328.