You can simply use HStack to separate the name text and its corresponding image. import SwiftUI struct ContentView: View { var body: some View { TabView{ FirstView() .tabItem { HStack { Text("Save") .fixedSize() Image(systemName: "lock.fill") } } SecondView() .tabItem { HStack { Text("Things") .fixedSize() Image(systemName: "message.fill") } } } } } struct FirstView: View { var body: some View { Text("First") } } struct SecondView: View { var body: some View { Text("Second") } }

At which line do you write a file to the triggersDirectory folder? 'triggersDirectory' appears three times, but I don't see that. You do write a file to the reflectionsURL folder.

As long as your application already has a functional ability for those who use it with free of charge, I don't see a problem.

Personally, I think it's a SwiftUI bug. I have a similar problem with the ImageRenderer class and get the same symbol. I've filed a feedback report. It's been 5 or 6 weeks. When I filed a bug report 9 or 10 years ago regarding Core Graphics, I had to wait for 3 months. If possible, you may write code in Cocoa and use it as NSViewControllerRepresentable or NSViewRepresentable.

The deployment target is iOS 16.

I've made some change the App View as follows. import SwiftUI @main struct LocaleSwitchCrazyMamaApp: App { @StateObject var lanSetting = LanguageSetting() var body: some Scene { WindowGroup { ContentView() .environmentObject(lanSetting) .environment(\.locale, lanSetting.locale) } } } The outcome doesn't change, though.

I guess I shouldn't do it after reading https://developer.apple.com/forums/thread/78244 .

Hmm... Suddenly Susan, the app can now list records after I put the rows under the body guy in VStack.

You are not employing the color scheme on Text("Text"), are you?

Employ the color scheme inside the snapView guy. @ViewBuilder func snapView() -> some View { VStack { Text("Text") .background(colorScheme == .light ? .yellow : .brown) Text("Test2") .background(.green) snap snapEx() } }

I've removed the optional part in the framework as follows. And it works. I don't know why the callBack guy can't be optional, though, in the framework. import SwiftUI public struct ColorSelectorView: View { @Binding var selectedColor: Color @State var callBack: ((Color) -> Void) let colors: [Color] = [.blue, .green, .orange, .yellow, .red, .purple] public init(selectedColor: Binding<Color>, callBack: @escaping ((Color) -> Void)) { self._selectedColor = selectedColor self.callBack = callBack } public var body: some View { HStack { ForEach(colors, id: \.self) { color in Image(systemName: selectedColor == color ? "record.circle.fill" : "circle.fill") .foregroundColor(color) .onTapGesture { selectedColor = color callBack(color) } } } } }

In order to make a framework, I'm choosing to make the CallBack closure not optional.

I guess it has to be optional. Ugghhhh...

A. Open a new view with Sheet or equivalent? B. Navigate to a new View to NavigateLink? C. Use NavigationSplitView?

I could do it with Combine. But that's not what I need. I need a solution with a custom binding.