There is something surprising me in the screenshot: you have 2 versions referenced for release (17.0 and 16.0 iOS). Why is it so ? You should also have a look at the build settings of the PROJECT and check if what you have here (it might be empty, but should not iOS be 12 for instance):

Welcome to the forum. But the forum is not really intended for such "warnings". It is to help solve issues. The fact is not that reviewer does not want you to update, it is that in the new review, he/she has evaluated your games as spam (for good reason or not, that's a question we cannot answer). Have you answered to the review explaining why you consider your apps are not spam ? You have certainly read the guidelines; it may help you understand the reason for rejection and better explain in your comments: 4.3 Spam (a) Don’t create multiple Bundle IDs of the same app. If your app has different versions for specific locations, sports teams, universities, etc., consider submitting a single app and provide the variations using in-app purchase. (b) Also avoid piling on to a category that is already saturated; the App Store has enough fart, burp, flashlight, fortune telling, dating, drinking games, and Kama Sutra apps, etc. already. We will reject these apps unless they provide a unique, high-quality experience. Spamming the store may lead to your removal from the Apple Developer Program. You didn't provide any information that could help to help you, so a few questions: Are your 2 games similar ? that could fall in 4.3.a and cause rejection of both What type of game is it ? Is it in a very crowded game category ? that could fall in 4.3.b Have you identified games that are close to yours on the appstore ? Finally, it is not because app was accepted in a previous review that it will be in a next one. It may just mean that issue was not detected before. Good luck.

Welcome to the forum. programming tool and that is, they are not compatible with Sequoia 1.15.1. This includes Xcode What is the incompatibility you get ? C++ is supported in all versions of Xcode: https://developer.apple.com/xcode/cpp/ And Xcode can of course be installed on MacOS 15.1. PS: the exact OS number is MacOS 15.1

What code do you mean precisely ? Now, all apps which are published or notarised get a unique ID. This ID "knows" about the developer identifier. So, AFAIU, that contains somehow the "creator code". PS: why do you mind ?

The mechanism for style in containers is deep into Swift design. So it is unlikely to change. Replacing List by ScrollView should give you what you're looking for.

Did you explain this very clearly in the comments to reviewer ? With proof that you were effectively the owner of the other account ?

Welcome to the forum. Please explain when and how this occurs. Is is UIKit, in storyboard ? SwiftUI ?

@Vision Pro engineer So, would this statement be correct ? To work properly, SwiftUI with Xcode 16 requires at least macOS 15 If so, it should be in the release notes, at least as a known issue.

My response: Which features are not account-based? Only you can tell.   You need an account to play the game. That's the problem. The rule is that user must be able to test the app before creating an account (even more if it is a paying app). We don't know your game, so it's just a guess. Could you allow user to play as guest, with limitations : level of gold always restarts at 0, you can only jump from level 1 to 2… ? And finally, did you request a 30-minute online meeting with an App Review expert to discuss the guidelines and best practices for a smooth review process.

@GRALInfo Thanks for this additional testing. Using AppStorage (for a simple Bool) was an early design decision as the property isDarkMode is used in many views. So I could effectively use an environment variable and initialise in .onAppear or in an init(). I'll go this way if the bug is not corrected (I now definitely think it is an Xcode 16 regression). But falling on such issues in development environment is making me a bit nervous, wondering what else may be broken ? @VisionPro Thanks for the link. It is another way of doing it, but that denies the simplicity of AppStorage. If it is not corrected in a future Xcode release, does it mean that AppStorage is on obsolescence path ?

Welcome to the forum @calmnight. Yes you can. You will find any version of Xcode for download here, as well as useful information: https://xcodereleases.com

@GRALInfo, thanks for the test and the information. Effectively that could be an incompatibility with MacOS < 15. Which nevertheless is an issue, if we cannot keep the apps running correctly on not so older OS versions. To fully assess the point, would you have the opportunity to test the app produced by Xcode 16 on an older OS ? I'll post the answer if I get from FB.

I created a minimal project in Xcode 15.3 to reproduce the issue (run on MacOS 14.7). When compiled with Xcode 15.3, the toggle switches from light to dark mode. When compiled with Xcode 16 (16.0 or 16.1ß3), the toggle has no effect. I attached the complete project to FB report. import SwiftUI @main struct DarkModeTest_MacApp: App { @AppStorage("isDarkMode") private var isDarkMode = false var body: some Scene { WindowGroup { ContentView() .frame( minWidth: 300, maxWidth: .infinity, minHeight: 200, maxHeight: .infinity) .preferredColorScheme(isDarkMode ? .dark : .light) } .windowResizability(.contentSize) } } import SwiftUI struct ContentView: View { @AppStorage("isDarkMode") private var isDarkMode = false var body: some View { VStack { Image(systemName: "globe") .imageScale(.large) .foregroundStyle(.tint) Text("Hello, world!") Button(action: { isDarkMode.toggle() }) { Text("Toggle") } } .padding() } } #Preview { ContentView() } Additional information: It works on iPad (simulator).

So, what is your question ? Just do what reviewer asked to do.

I tried with 16.1ß3, same issues. However, if I set the background manually on a view (with colors that mimic the preferredScheme), it works: .background(isDarkMode ? Color.veryDarkGray : `Color.lightGray)` But having to do it on any subview is not a viable solution. So for the time being I stay with 15.3, but that's not a sustainable option either. Could it be a compatibility issue between Xcode 16.x and MacOS 14.y ?   Also, are you able to try with macOS 15.1? This is a Mac app, right? I cannot try with MacOS 15 at this time. And in any case, app has to run on versions below (down to MacOS 12 in fact), so that would not solve the problem. The app (SwiftUI) runs on MacOS and iOS I also tested the app by setting the Mac to dark mode. App does not adapt to dark. So it is just as if, with Xcode 16, preferredColorScheme was ignored. Could it come from AppStorage (but once again, it worked in Xcode 15).