3 ms·
Probably SwiftUI dependencies - onChange was changed in 17 which breaks and complicates a lot of code
by anonymouse008 3y ago
Probably SwiftUI dependencies - onChange was changed in 17 which breaks and complicates a lot of code
loading thread…
3 ms·