| < How to fix “Modifying state during view update, this will cause undefined behavior” | How to fix “Fatal error: No ObservableObject of type SomeType found” > |
How to fix “Protocol 'View' can only be used as a generic constraint because it has Self or associated type requirements”
Updated for Xcode 12.0
This is a particularly confusing problem, and it occurs because SwiftUI relies heavily on opaque return types. The problem happens because of code like this:
struct ContentView: View {
var body: View {
Text("SwiftUI")
}
}It feels like such a tiny thing, but the body property is declared as returning View rather than some View. The difference is small but important – you can find out more about it in my article How to use opaque return types in Swift 5.1.
So, to fix the problem use this instead:
struct ContentView: View {
var body: some View {
Text("SwiftUI")
}
}
SPONSORED Announcing NSSpain 2020: Remote Edition! An online, continuous conference for iOS developers. We’ll start on Thursday and finish on Friday, with talks, activities, and lots of fun for 36 hours, non-stop. Sound good? Join us!
Sponsor Hacking with Swift and reach the world's largest Swift community!
Similar solutions…
