How to fix "No exact matches in call to initializer" error in Swift

While coding, you might come across this error.

No exact matches in call to initializer

It can happen in many places. Based on the message, it might not be obvious what is causing it and how to solve it.

In this article, we will learn what is causing it and how to solve it.

Cause of the problem

The "No exact matches in call to initializer" error can happen when you initialize any type, e.g., String, ForEach, UIColor, Date, etc.

The cause is the provided argument type isn't supported by any of the initializers on that type.

You can easily support sarunw.com by checking out this sponsor.

Translate your app In 1 click: Simplifies app localization and helps you reach more users.

Try it for Free

Solutions

I can't provide a solution that covers every case since there are countless data types and arguments, but I can give you an example.

Here is an example where we get the error on SwiftUI Text.

struct BadgeView: View {
    // 1
    let count: Int
    
    var body: some View {
        // 2
        Text(count) // No exact matches in call to initializer 
    }
}

1 count is an Int.
2 We provide count as an argument for a text view initializer, but no initializer accepts an Int, hence the error.

To fix this, we need to convert an integer to one of the supported types. In this case, I convert it to a string.

There are different ways of converting an integer to a string. I can give you two.

Text(count.description)
Text("\(count)")

With these small changes, the error is gone.