Toaster not clearing on first call about alerttoast HOT 5 CLOSED

Same issue here

from alerttoast.

Hey, any workarounds? Seems this is not getting fixed

from alerttoast.

I have been looking at this and believe I have a fix. I'll raise a PR with my modifications.

The issue relates to changing from one displayMode to another. It actually occurs not just on the first call, but any time a new AlertToast is created with a different displayMode. Since the initialiser defaults to .alert, and first call is actually the second call (the first being the initialisation), the task to take the toast down is never created.

So, the workaround (without my changes) is to create the first AlertToast with the displayMode you intend to use throughout the rest of the app:

In your example @pulpfree, change this:

    @Published var toaster = AlertToast(type: .regular) {

to this:

    @Published var toaster = AlertToast(displayMode: .hud, type: .regular) {

The workaround does not work if you want to use more than one displayMode in the same app.

from alerttoast.

Hey @pulpfree ,
I tried to reproduce this bug but with no success.
I guess that DispatchQueue you've put in the sink operator has to do something that causes this kind of problem.
It's always better in Combine to use the .recieve(on:) operator and not create a new thread inside the sink.
Also, check your custom operator to check for any problems there (resultPublisher).

If you strip down your ObservableObject and keep only the Published variable you will see that it works as it should.

from alerttoast.

Hey @elai950. Thanks for the info, appreciate it.

from alerttoast.