I suggest you read all App Review Guidelines if you haven't. The description of the app you provide seems to violate 4.2 Minimum Functionality. If the main function of your app is to show a book content, whether or not you have invested tens of millions of dollars developing it, whether or not you hired someone to compose music, it's still a book, isn't it? Your book has a unique story. And therefore, it should be admitted, you mean? You may want to have a content that a book can't have.

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

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

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

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

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) } } } } }

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() } }

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

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

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

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.

The deployment target is iOS 16.

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.

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.

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.