I requested that they approve my version to solve other details I do doubt they will even consider it. You have to comply first, then they may approve. Did you explain (in the comments to reviewer) why you think you comply ? That's the best way to get your voice heard.

If you use directly Image, it does not work. You have to use the Image built from a resized UIImage. That would be worth a bug report. Get a solution here: https://www.hackingwithswift.com/forums/swift/remove-or-resize-an-image-when-selecting-an-item-in-a-picker-view/23940 Here is the full code. Fiat 500e is an image in Assets struct ContentView: View { struct Data: Identifiable, Hashable { var id = UUID() var name: String var condition: Bool } @State var selection = "Easy" var datas: [Data] = [Data(name: "Easy", condition: true), Data(name: "Medium", condition: false), Data(name: "Hard", condition: true)] var myImage: UIImage = UIImage(named: "Fiat 500e") ?? UIImage() var resizedImage: UIImage { return myImage.scalePreservingAspectRatio(targetSize: CGSize(width: 50, height: 25)) } var body: some View { Picker("Title: ", selection: $selection) { ForEach(datas, id: \.self) { data in HStack { Text(data.name) if data.condition { Image(systemName: "globe") } else { Image(uiImage: resizedImage) .resizable() .scaledToFit() } } .tag(data.name) .padding() } } } } extension UIImage { func scalePreservingAspectRatio(targetSize: CGSize) -> UIImage { // Determine the scale factor that preserves aspect ratio let widthRatio = targetSize.width / size.width let heightRatio = targetSize.height / size.height let scaleFactor = min(widthRatio, heightRatio) // Compute the new image size that preserves aspect ratio let scaledImageSize = CGSize( width: size.width * scaleFactor, height: size.height * scaleFactor ) // Draw and return the resized UIImage let renderer = UIGraphicsImageRenderer( size: scaledImageSize ) let scaledImage = renderer.image { _ in self.draw(in: CGRect( origin: .zero, size: scaledImageSize )) } return scaledImage } } The image displayed in selection is now resized (it was automatically resized in Picker): In Picker. After selection.

declare quotes as a computed var var quotes: [(quote: String, order: Int)] { var output = [[(quote: String, order: Int)]] () // loop 1 to 4 // Compute each line as you do in getPrice // append to output return output }

We cannot invent line 34…

This forum is not the right one for a direct request to Apple. Did you contact and appeal the review team ? Note that functional app does not mean it means minimal functionality requirement.

It crashes also on simulator. Crash comes from: ForEach($viewModel.filteredPeople, id: \.name) { person in Reason is that when you type in search, because of didSet, you update the filtered but the forEach is still using the full array ans waits for a 4th person which does not exist any more.

That's for the version, but have you checked the build number ? What is the build number of each version ? Build number must always be higher (alphabetical order) than the previous version. Note also that this forum is not the best place to contact Apple. You'd better directly contact support: https://developer.apple.com/contact/topic/select

Very nice. How do you use it in your app ? But effectively, I would not do it, it is too close to Apple's design and could be considered as some try to lure people into believing your app is an Apple app.

We continue to get the same spam and the same automatic and irrelevant reply from some App Store Connect Engineer.

Maybe this can help. They explain how to have a SVG recognised in Xcode. https://stackoverflow.com/questions/57243071/how-to-format-customized-sf-symbols-svg-files-for-import-into-xcode11

Yes, just saw it. So they've probably awaited for the 16E announcement.

It cannot be eliminatory, as it is not a video but depends on how the reviewer tests your app. So, as far as I understand, it is more a (strong) guideline than a requirement. My understanding is that reviewer have a limited time and may stop the test after 3 minutes. So that's you to decide to take the risk or not. But take care, it must be possible to appreciate your app in 3 minutes, even if not completely explored.

Welcome to the forum. This forum is for developers who need help or advice for developing their apps. It is not about software use, unless they are development tools. And it is not an official channel to Apple. You'd better post on the Apple Support Community: https://discussions.apple.com/welcome, or file a bug report. https://feedbackassistant.apple.com

Very strange indeed. I've tried using RuleMark as explained here: https://stackoverflow.com/questions/78873602/reverse-y-axis-of-swiftui-chart But get the same flipping. It does not occur if all values are equal but non zero: let data: [Double] = [10, 10, 10, 10, 10] Looks like a side effect of a "zero divide" (between the default minimum zero of y axis and the found max which is also 0) : when all values are equal, it wrongly computes the orientation (as you will see, chartYScale corrects this by providing the orientation). You should file a bug report. I found a solution using chartYScale: struct ChartView: View { let data: [Double] = [0, 0, 0, 0, 0] var body: some View { Chart { ForEach(data.indices, id: \.self) { index in LineMark( x: .value("Index", index), y: .value("Value", data[index]) ) } } .chartYScale(domain: [0, 50]) // <<-- Added this .chartYAxis { AxisMarks(values: [0, 10, 20, 30, 40, 50]) { value in AxisValueLabel() AxisTick() AxisGridLine() } } .padding() } }

Welcome to the forum. My advice as you once experienced a rejection, is to add a comment to the reviewer, each time you submit a new version, explaining exactly what you tell here. App was once rejected under 4.3, but after adding unique features it was accepted . These included: ✅ Public tracking profiles ✅ Widgets for stats ✅ Background fetch for updates ✅ No login required That will help a new reviewer to perform an better informed review taking into account that you have corrected what caused a former rejection.