swift | the multiparty transport protocol

You need to use self.

You need to set input image for the filter and take care of the interoperately between Image and UImage

My advice would be: don't try this in a playground. Playgrounds aren't ready for this stuff yet. Your code compiles and runs fine in a real project. Here's an example:

The reason seems to be explained in the source:

While editing my initial question to add more context as Jay proposed I think it found the issue.

What probably happens? The view where the crash is, contains a table view. Each cell will be configured before being presented. I use a flag which holds the information, if the amount of weight for this cell (it is a strength workout app) has been initially set or is a change. When prepareForReuse is being called, this flag has not been reset. And that now means scrolling through the table view triggers a DB write for each reused cell, that leads to unnecessary writes to the db. Unnecessary, because the exact same number is already saved in the db.

My speculation: Scrolling fast could maybe lead to a race condition (I have read something about that issue with realm) and that maybe causes this weird crash, because there are multiple single writes initiated in a short time.

Solution: I now reset the flag on prepareForReuse to its initial value to prevent this misbehaviour.

The crash only happens when the cell is set up and the described behaviour happens. Therefor I'm quite confident I fixed the issue finally. Let's see. -- I was not able to reproduce the issue, but it also only happens pretty rare.

I was once in your shoe before and came across this Open source library called particle animations.

I would NOT recommend using the library itself since it's deprecated. But I would recommend referring to its source code to get an idea of how to use CAEmitterLayer and CAEmitterCell to make the looks of a Fire!

As you could see from its readme, it has direct examples of Fire. It also states that even Apple and Facebook uses CAEmitterLayer and CAEmitterCell to produce the effect of a fire.

Feel free to ask for more questions.

Users of external identity providers have to be registered before the can login.

You can find the details here: https://developers.tapkey.io/api/authentication/identity_providers/#working-with-users

When it is necessary for your use case, that these users are automatically created when they login, please send a request to tapkey support and they will enable this feature for you.

I'm the author of the article you referenced.

As discussed in Discover concurrency in SwiftUI, views can make use of the new .task { } and .refreshable { } modifiers to fetch data asynchronously.

So you now have the following options to call you async code:

You can try this -