that they need more time to review it. It usually is not a notification of rejection, just telling that the review for your app will need more time. (It represents that in the pre-review process, your app has some suspicious points. This can be caused by some third party libraries which is not properly using APIs.) Does the notification really contain the terms that your app is rejected? almost two weeks have passed Once your app is marked as need more time, more than two weeks is not a rare case. Sending sort of claims might reset the reviewing process, and another more than two weeks may be needed. Just wait for a few weeks till you get the actual review result: approval or rejection.

Have you sent a feature request using the Feedback Assistant?

But that doesn't sound like a clean solution.  Why do you think so? That sounds like the right solution for me.

Thanks for showing your code. Unfortunately, the session video was made while SwiftUI was in beta, and you need to make the code updated in many, many points. And BindableObject having didChange does not work in the released version of SwiftUI. Please try this: class RoomStore: ObservableObject { // Instead of BindableObject @Published var rooms: [Room] //Use `@Published` here, no need to use `didChange` init(rooms: [Room] = []) { self.rooms = rooms } } There are many good tutorials and sample codes written for the released version of SwiftUI. You should better find a good one unless you want to study how the beta version of SwiftUI was.

The session 10002 of WWDC21 has nothing to do with your issue. Using the right tag would help getting better responses.

It seems the min and max functions abort the sieve if the first pass doesn't yield a value. The closure passed min or max needs to be consistent in comparing orders. In a consistent ordering, one (and only one) of the following gets true: a < b a == b a > b Your closure {$0 != 0...0 && $1 != 0...0 && $0.lowerBound < $1.lowerBound} may return false, for both yourClosure(a,b) and yourClosure(b,a) even when a != b. Don't you think it is strange for a comparison function? In the header doc of min or max, you can find this description: The predicate must be a strict weak ordering over the elements. That is, for any elements a, b, and c, the following conditions must hold: areInIncreasingOrder(a, a) is always false. (Irreflexivity) If areInIncreasingOrder(a, b) and areInIncreasingOrder(b, c) are both true, then areInIncreasingOrder(a, c) is also true. (Transitive comparability) Two elements are incomparable if neither is ordered before the other according to the predicate. If a and b are incomparable, and b and c are incomparable, then a and c are also incomparable. (Transitive incomparability) It is not clear enough, but I guess you want to do something like this: import UIKit /* let ranges = [ //1...4, 0...0, 0...1, 3...5, 0...0, 2...4, 3...7, ] */ let ranges = [ 1...4, 0...0, 1...6, 3...5, 0...0, 2...4, 3...7, ] let defaultMinValue = 0 let ordinateMinimum = CGFloat( ranges .filter{$0 != 0...0} .min(by: {$0.lowerBound < $1.lowerBound})? .lowerBound ?? defaultMinValue ) let defaultMaxValue = Int.max let ordinateMaximum = CGFloat( ranges .filter{$0 != 0...0} .max(by: {$0.upperBound < $1.upperBound})? .upperBound ?? defaultMaxValue ) print("ordinateMinimum: \(ordinateMinimum)\nordinateMaximum: \(ordinateMaximum)") One more. You should not include two or more topics in a single thread. For example, if you made a separate thread for this min, max issue, more readers who were suffering from the same issue would be able to find the thread more easily.

I know openSettingsURLString redirects to app-settings and we can press back to go to general settings. Is it possible to go to settings page directly? As already noted, the answer is NO. One thing you need to care is that you can find many sites showing some urls to go to settings directly without any cautions or notes. Using such urls may be considered as using private APIs, and can be a reason to be rejected in reviewing for the App Store.

Contact to the author of the app. This is not a place to request a invitation code of some specific app.

Sorry for the late response. With lacking Item or some other parts, I needed to find some chance I could spend plenty of time. Only iPad. Have you tried adding navigationViewStyle? NavigationView { //... } .navigationViewStyle(StackNavigationViewStyle())

You know it's hard to reproduce something when external services such as Firebase are used. So, this is just an impression glancing your code, but why are you calling unneeded reloadData()? Generally, you have no need to call reloadData() when you properly call deleteRows(at:with:). Please try removing reloadData() in tableView(_:commit:forRowAt:). One more, you should better check the value of editingStyle in the method.

Thoughts how to solve it? Wait till the released version of macOS Server for Monterey will be released. (Generally, macOS Server may be updated more than a few months later than the macOS updates. You should better not update your macOS immediately if macOS Server is required for your work.) Or else, you can try the beta version of the next macOS Server. (Visit the Downloads page.)

What is the proper way of defining that the row.text is a binding in this case? As far as I read the docs and watched the sample code, SwiftUI.Table does not give us a quick way to make some cell editable. One possible solution would be something like this: (Not sure, if this code would work as expected.) struct ContentView: View { @State var data = [ Thing(id: 1, text: "one"), Thing(id: 2, text: "two"), Thing(id: 3, text: "three"), ] var body: some View { VStack { Text("Hello, world!") .padding() Table(data) { TableColumn("ID") { row in Text(String(row.id)) } TableColumn("Text") { row in //`id` needs to keep the position in `data` TextEditor(text: $data[row.id-1].text) } } } } } at the end the Thing will also be some dynamic structure not known at compile time That sounds like you should better stay in the AppKit world a little more, until SwiftUI gives us more convenient ways to write some dynamic things.

Apple's developer site is not a place to exchange redeem code things of some specific app. Contact to the author of the app.

I cannot reproduce the same result with your code. (iPhone 13 mini simulator, Xcode 13.1) Can you clarify how you get the result as shown in your screen shot?

You cannot run Xcode on a HP laptop, even if you successfully download Xcode.xip.