My advice. If you ever had a rejection, add a comment for reviewer in any submission of the app, explaining the situation: that app was first rejected and then approved after appeal. That may avoid a new reviewer to make the same rejection error because of lack of context.

Is it a Mac App ? If so, normal that app appears in a window. There is no simulator for Mac app, as they run native on the Mac. For the error message, probably a solution here. https://github.com/flutter/flutter/issues/150227 Edit scheme select Run Go to Diagnostics Disable Metal API verification

No other developer can help for questions related to submission, but maybe give some advice on how to proceed.. Did you contact support ? https://developer.apple.com/contact/ What are the reasons of rejection ? Could you show the complete message ? What type of app is it ? Note: in your new submission, did you explain in reviewer's notes the changes you made since last rejection ?

Problem is that a swipe action has its own styling that is applied by the system. See details here: https://stackoverflow.com/questions/73783291/set-image-color-in-swipeaction So, one workaround is to create and use your own image with the white trash inside a red circle. .swipeActions(edge: .trailing) { Button { print("custom") // Your code here } label: { Image(uiImage: UIImage(named:"Trash in red circle")!) .frame(width: 50, height: 50) } .tint(.white) Here is the result: The trash icon named:"Trash in red circle": The swipe: Hope that helps.

Where did you find this ?

At what stage precisely do you get the error ? Starting from the VisionOS template, in Xcode 16.2, I was able to Archive (for validation). I just had to add the icons and give a name that was not yet used.

worth is a positive evaluation. That means you appreciate iPhone 16 or you don't speak English correctly.

I tested your code on Mac Sonoma and Xcode 16.2. I did not notice the difference between the various cases unless I really focused to try to notice. And it is nearly imperceptible. It seems to occur only when a new row appears at the end of scrolling.

Following on @darkpaw point, what is the unsolved user pain point, or expectation, you want to solve. You have first to dig into the problem, to make sure its solution would have real value. Then you'll start developing.

This appears to be a known issue, depending on the color scheme used by iOS 18 for different situations. there is apparently no work around: https://www.reddit.com/r/iphone/comments/1gginzy/color_inaccuracy_since_ios_18/?rdt=38756 I found this hint: https://www.reddit.com/r/iOSProgramming/comments/3enzxl/background_color_for_uiview_rendering_slightly/ I tried to change the color scheme, but I did not found the right one (is it sRGB, P3, Device RGB…):

I tested on a device (iPhone XS) iOS 18.2. I effectively notice a small difference ; hardly perceptible visually, but clear on screenshots. Bizarre. Launch screen                                                                    Main screen So I used Digital Color meter to check. In native values I get Launch 255 14 27 Main 234 50 34 In P3 values I get Launch 255 2 0 Main 234 50 34 In sRVB values I get Launch 255 0 0 Main 255 1 0 I don't know what conclusion to draw from this however…

I tested in simulator (iOS 18.2) and do not see the difference. Could you show how you defined colors (it is really pure red in both cases, or one is systemRed for instance ? Here the screenshots with #ff0000 (red) in both cases (Label is in a systemRed view:

There are good tutorials on the web. This one as example: https://medium.com/@dhanush_kumar/modularizing-your-ios-app-frameworks-vs-swift-package-manager-7fdf9a127261

I created "Test Hello", a SwiftUI project in Xcode 16.2 (that's what you call Hello world project). I set the minimum target to 15.6 as shown below: I then tested successfully on iOS 16.0 simulator.

If understand, you call rotate then translate ? Could you show how you create the transforms ? In your case, I think it should be: var t = CGAffineTransform.identity t = t.translatedBy(x: deltaX, y: -deltaY) t = t.rotated(by: rotation) so when you apply t = Id ° trans ° rot, you apply rot first. If you call sequentially, this may help: https://stackoverflow.com/questions/24926062/sequence-of-cgaffinetransform-on-a-single-uiview Note: I also had to test and try before getting the expected result.