It is very explicit in guidelines, if your Previews don't show real screenshots, the app risks being rejected. 2.3 ASR & NR Accurate Metadata.                  Customers should know what they’re getting when they download or buy your app, so make sure all your app metadata, including privacy information, your app description, screenshots, and previews accurately reflect the app’s core experience and remember to keep them up-to-date with new versions. You can add drawing in screenshot overlay: 2.3.3 Screenshots should show the app in use, and not merely the title art, login page, or splash screen. They may also include text and image overlays (e.g. to demonstrate input mechanisms, such as an animated touch point or Apple Pencil) and show extended functionality on device, such as Touch Bar. You can use AI to generate images to include in the app and they will show on screenshots. Or some image to partially overlay the screenshot. But not substitute to screenshots.   it just ignores the dimensions I tell it to use That's not the issue as it is so easy to resize to the exact dimensions. The issue is the content.

@petriniemela Welcome to the forum. How do you see your app is not distributed ? It does not appear on the AppStore ? Have you checked that you have set the countries for distribution properly (is Finland in your list) ? You answered in the comments (better to answer with a reply, more visible). Ready for distribution is the last stage, no need for more. Did you receive a mail notification ? If you still have issue, the best is to contact support. https://developer.apple.com/contact/ If you want someone else to check, could you give the name of your app ? Note: avoid duplicating posts.

It is stated effectively that "All content must be in English." IMHO proper names can (should) be in their native language, as long as it is clear that these are names and not some casula text.

That's really painful situation to get such a rejection after a long development. The fact that Apple maintained that the app “duplicates the content and functionality of similar apps in a saturated category." may hint that rejection was because your app is in a very saturated category, where all apps end up looking similar, even when you really did your own design without any copying. Could you tell what type of app it is. Unless you change the app to get out of this category (easy to say, hard to achieve), I fear it will not be accepted. From my experience, I found that posting a message for the reviewer in the submission file may help. So, what I would try in your case: Make some change to the app (not a complete redesign, but something visible), to have a reason to resubmit May be change the name of the app so that it looks more different in the category Explain, in the notes to reviewer, how your app is different from others in the category, what changes you made to make it different (this is more to prove your goodwill than to provide in depth analysis). Good luck.

I just tested on an iOS 26.2 device. It seems that try await AgeRangeService.shared.isEligibleForAgeFeatures does nor respond. Is it because Apple has paused on SB2420 ? In this code func testAgeRange() async -> Bool { do { print("Calling isEligibleForAgeFeatures") // show on console var isEligible = false print("iOS 26.2 or later") // show on console isEligible = try await AgeRangeService.shared.isEligibleForAgeFeatures print("isEligible", isEligible) // Does not show on console if !isEligible { print("Not in Texas") return true // Not in Texas, so we can proceed } } catch { print("error", AgeRangeService.Error.notAvailable) // Does not show on console return true // we accept anyway if no ageRange provided, in order not to cause problem out of Texas ? } Here is the console content: Calling isEligibleForAgeFeatures iOS 26.2 or later

If you were to redevelop, that could not be the same app, as it would be rejected as spam.

Is it acceptable to include placeholders for features that aren’t supported by Swift Playgrounds, or features I planned but didn’t have time to fully implement (as long as the core experience works)? IMHO, that would be a bad idea, even if it were not forbidden; what would be the value for reviewer?   My app relies a lot on user inputs. Is it okay to include a button that loads sample data for reviewers, or is there a preferred approach for this? App must be tested in 3 minutes. No time for a lot of user data. So, providing demo data may be a workaround, but capability to enter personal data is part of user experience. Couldn't you have some predefined (but modifiable) data but let user enter a few (less than 10) important data to experiment your app ?   Besides the known constraints (< 25 MB, experienceable within ~3 minutes), are there any other limits, e.g. lines of code or overall app complexity All requirements are in the terms and conditions for submission. Read them carefully. If I remember well, there are also requirements on copyright. Check you meet these conditions: If your submission includes any open source software, music, photos, artwork, or any other content that you do not have ownership rights in, you agree to (a) comply with all applicable licensing terms and copyright obligations and (b) provide an explanation of why it was used.   Can AI-generated assets (e.g. images) be used if they’re clearly labeled as such inside the app? What type of asset beyond images do you mean? If they are illustration images, I don't think it is a problem.   Do we need to explicitly document where AI was used (assets, code, etc.) as part of the submission? AFAIK, no. Notably because Xcode uses AI for predictive coding. However, you should avoid to have the app fully generated by AI which would probably be a negative point if detected.   My app uses the Foundation Model: On what device is the submission evaluated and should the usage of the Foundation Model be explicitly marked for reviewers? In the terms and conditions "On-device Apple Intelligence frameworks and other Apple technologies may be used. So no need to mark it. Good luck.

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…