Who do you ask the questions to ? If the spec is not published (I assume you did perform a web search), developers here will not likely have the information. If you want to ask directly to Apple, the forums is for developers and may not be the best place "for academic verification"

Maybe I miss something but isn't it already available? date created: Newest date of last activity: Last updated Sorry for the ridiculously large image. I filed a bug report on this.

Yes, situation has much improved since Jan 5th. They are visibly handling the backlog. A few more hours of patience I think.

@darkpaw: I have effectively noted that Xcode 26 automatically adds this copy from time to time. I now know this reason, the YES.

The review pipe was certainly saturated over the new year break for 6 to 8 days. But it started to flow again on Monday 5th. So be a bit more patient (even if 10 days is a very long wait), it should go soon in review.   I removed that build and resubmitted this past Saturday (Jan 3). Don't remove submission to resubmit. That could cause additional issues and delays. And you have returned to the back of the line. Did you contact support directly ? Good luck.

Could you be more precise on the problem you face ? Have a look here on how to post on the forum: https://developer.apple.com/forums/thread/706527

The following code segments run when building and running the app, or after going home and re-opening the app, but now when quitting the app and re-opening it again. What code can do that? Please be more precise in explaining the use case and what they mean exactly after going home and re-opening: what do you do exactly when you quit: what do you do precisely ? What do you get ? What did you expect ? explain what you get printed for each of the cases. Note: you should have more discriminant print: init() { print("init test") } .onAppear { print("onAppear test) } .onChange(of: scenePhase) { _, newValue in print("onChange \(newValue)") }

Welcome to the forum. Is it just a warning or does it stop compiling and build ? If just a warning, you can ignore. There are 2 libraries that propose the same function. You may however try a clean build folder (Product menu) to clean derived data. If you are in debug mode, change to release mode, to see what happens. To change mode: Edit Scheme…

"In Review" status for 4 days on a resubmission. Do you mean you cancelled and resubmitted ? If so that may be the cause (I've noted it may create issue, blocking or delaying the process). Did you contact support ?

@135_110 My guess is that the most important was finding the right idea for the app, that looks original and fun to use. Note it is required that it showcase Apple's platform capability through the wise use of API. For the coding, I would not be surprised they spent hundreds of hours to fine tune their app. But let's them say if they get the post. And go this year, at least to get your feet wet. You'll learn for seriously competing next year. Good luck.

Welcome to the forum. Your question is too general to get a precise answer. However: cancelling a build and resubmitting does put you back in the pipe. but as we don't know how the pipe is managed, hard to say if to go to the back of the queue or not. But most likely, you will fall back in the line. I‘ve done this multiple times, and I have users asking me when the updates are coming. In general, it is not a very good idea to cancel a submission. I have noted that it may create problems, even blocking submission. you'd better test your app seriously before submitting. Guidelines remind that review board is not to detect bugs.

Flow has restarted this morning. You should be in review very soon if not already the case.

App has been reviewed, after the week end as expected.

Have you also declared files in their lproj folders, for each language (en.lproj, it.lproj, fr.lproj…? They should contain at least the following files in each: May read this for further explanations: https://mixable.blog/why-does-the-ios-app-store-show-more-languages-than-my-app-supports/

It visibly has nothing to do with the app or the developer's account. Just the pipe is pretty much filled.