If you publish a software title that shares same features with an existing one, it can be rejected. Some reviewers check and see if you already have one or more similar titles. You can get a flat rejection. Or they may suggest that you provide new features as add-ons to an existing software title. So you may consider offering in-app purchases. Of course, you can play dumb and submit a new title, which carries a risk of being rejected not now but later on.

If you don't like their rules, you are free to open your own online store and sell your products. Nobody can stop you. And you can be bitter for as many weeks and months as you want, thinking about how much money you have lost except that a stranger doesn't care. I would rather either accept a defeat and move on with my life or adjust the product such that it would be allowed into the store, examining similar products of others.

We don't know what you have done. You should simply contact them and share your side of story with them.

What's 'view' in event.location(in: view)? If you are already in SpriteKit, not a view controller, that's the cause of confusion.

Because you didn't include in-app purchases when you submitted the app itself?

I submitted a software update 90 minutes, and it has already been reviewed and accepted. So your case is probably isolated. Perhaps, you have an entered a version lower than the current one?

If I were you, I would either accept a defeat and move on or download similar "interactive" books that you say are accepted into the App Store and find out how they make it. What I wouldn't do is take the case to the Appeals Board. The Appeals Board often takes the side of the reviewer FYI. If they do, that will be the end of your project.

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?