How did you switch them off ? Normally you select Show issues navigator (at the top of the left panel of Xcode-. Then ay the bottom, you have a Filter line. Click on the rightmost icon to turn on / off (show errors only or all warnings as well).

Welcome to the forum I really really don't like reading straight from the documentation (although who does honestly) Those who really want to get deep understanding on how things work… 😉 Some short synthetic doc that may help: https://developer.apple.com/documentation/gamekit/creating_turn-based_games this video series should provide most of what you need: https://www.youtube.com/watch?v=HmlW18K_q_c

Just open Bookmark navigator and delete the bookmark (select then backspace). If OK, don't forget to close the thread by marking this answer as correct. Good continuation.

Which version of Xcode did you use to generate binary ? Do you use any 3rd party library ? Maybe some useful info here ? https://forums.developer.apple.com/forums/thread/676166

Have you identified the concerned view ? When you've found, add the following test in this View's body: .onAppear { print("View appeared!") } .onDisappear { print("View disappeared!") } And tell what you see when bugging in simulator. Does it occur when you navigate very rapidly ? If so, that would probably mean that SwiftUI had no time to pop the view before pushing again. See old discussion here (not SwiftUI): https://stackoverflow.com/questions/7083124/pushing-the-same-view-controller-instance-more-than-once-is-not-supported-exce

Trader status is not linked to a specific app but to your organisation. I extracted and outlined some key points from: https://developer.apple.com/help/app-store-connect/manage-compliance-information/manage-european-union-digital-services-act-trader-requirements/ To determine if you're a trader, you should consider a range of non-exhaustive and non-exclusive factors (see those listed on page 2 in the EC’s Guidance), which may include: Whether you make revenue as a result of your app, for example if your app includes in-app purchases, or if it's a paid or ad-sponsored app — especially if you're transacting in large volumes; Whether you engage in commercial practices towards consumers, including advertising, or promoting products or services; Whether you're registered for VAT purposes; and Whether you develop your app in connection with your trade, business, craft, or profession—meaning that you’re acting in a professional/business capacity. You're unlikely to be a trader for EU law purposes if you're acting “for purposes which are outside your trade, business, craft, or profession.” For example, if you're a hobbyist and you developed your app with no intention of commercializing it, you may not be considered a trader. Regardless of whether you’re an individual developer or organization, if you have a legal status associated with a business activity, that would suggest you may be a trader. IMHO, from what you wrote, you develop the app in connection with your business, hence you should be considered as a trader.

Did you include the privacy manifest as required ? https://developer.apple.com/support/third-party-SDK-requirements/#:~:text=Third%2Dparty%20software%20development%20kits,obvious%20to%20developers%20and%20users. you must include the privacy manifest for any SDK listed below when you submit new apps in App Store Connect that include those SDKs

What darkpaw wrote, plus. You say it's crashing in AppDelegate. That may not be the case, that's only the crash is finally reported (in appDelegate) but did occur somewhere before. You should read in detail the excellent post from Quinn on how to report problem on the forum: https://developer.apple.com/forums/thread/706527 Have you the crash report ? Please show Are you using third party library like Firebase ? Please tell any other information that may be useful

Examples of unclear purpose strings: "App would like to access your Contacts" "App needs microphone access" That's what you want, that's not the reason why. Correct texts should explain what app will do with these accesses (of course your reason will probably be different: "App would like to access your Contacts to be able to send mail to contacts" "App needs microphone access to allow voice command" Of course, reviewer may check that this is how app uses the access. Be careful, if misleading or clearly false reason, your account could even be terminated.

It's not a bug. That's just to warn you that print may show an optional optional(some value) But you don't have to care for a print on the console. Please show complete code.

Welcome to the forum. No, you can submit an app that runs on iOS 17.2 and above. No requirement to make it run on lower versions. But you do limit your accessible market. So, that's your decision.

Reviewer message is very explicit: "We noticed your app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. Submitting similar or repackaged apps is a form of spam that creates clutter and makes it difficult for users to discover new apps." Even if you showed agreement between the 2 developers, that would not solve the issue. AFAIK, the only solution is to cancel one of the apps (the one that was rejected) and remove from Appstore. And post a comment to reviewer when you update the other app that the similar app has been withdrawn.

Does it occur for any custom font ? Which fonts ? Could you show the problem through detailed example (and possibly screen shots) ?

What was the cause of original rejection ? When there are such delays, it may mean that issue is not only the app itself but your account for which they are doing some investigation. Then submitting a new version does not help.

What should I do? Explain precisely what happens. How do you know script does not start ? Could you show the script ? Could you explain how you launch the script ? Note: it seems you never close your threads, even when you've got correct answer. You should do it to keep forum clean and let those who helped know that their answer solved the issue.