Yes, Auto Layout is a good starting point, as long as the constraints are flexible. Pin content to the safe area, avoid fixed widths and hard-coded screen assumptions, and let views resize with the available space. Apple's guide says standard system components adapt to iPhone Duo's different poses automatically, but custom layouts may need extra work around the hinge and reserved areas. Try your app on both the outer and inner displays in Xcode's Device Hub, and check that buttons, text, and navigation remain usable as the device opens and closes. Auto Layout can size and position views, but it can't decide whether a two-column layout still makes sense on the smaller display. Apple's guide: https://developer.apple.com/design/human-interface-guidelines/designing-for-iphone-duo

DancingCreatures is the name of a custom view in the lesson, not a special Swift command. The wording is a bit easy to misread. If the lesson has already supplied a DancingCreatures.swift file, adding that view means putting DancingCreatures() where the lesson wants it displayed. You do not need to recreate the whole view. For a step about a navigation link, it would go in the destination of that link. Could you post the exact instruction and the code around the place you are editing? That would make it much easier to show you the right spot. If it says it cannot find DancingCreatures in scope, check whether the file exists in the project and that the spelling matches, including capitals.

For the milliseconds part of Quinn’s example, you can convert the Duration like this: func milliseconds(_ duration: Duration) -> Double { let parts = duration.components return Double(parts.seconds) * 1_000 + Double(parts.attoseconds) / 1_000_000_000_000_000 } let clock = SuspendingClock() let start = clock.now // Do the work you want to time here. let elapsed = milliseconds(clock.now - start) print(elapsed)This keeps the fractional milliseconds too. SuspendingClock stops counting while the device is asleep. If that time should count toward your elapsed time, use ContinuousClock instead. https://developer.apple.com/documentation/swift/duration/components

I would hold off on paying again until Developer Support checks the existing purchase. A charge going through and the membership becoming active are separate steps. One thing worth checking is the account you used to enroll. Apple allows the Apple Account used for payment to be different from the enrollment account, so make sure the website is signed in to the enrollment account. You can check that in the Account tab of the Developer app. How long ago did the payment complete? Apple says to contact support if you have not received membership confirmation within 24 hours. Send the receipt and enrollment details privately through the support form so they can check the purchase against your enrollment. https://developer.apple.com/help/account/membership/program-enrollment https://developer.apple.com/help/account/membership/enrolling-in-the-app/

Since you have already checked Media Manager and saved, I would narrow this down to the saved screenshot placement rather than assume it is a color-profile issue. A few checks that may help: In the exact iOS version you are submitting, check the language selected at the top right and its iPad 13-inch screenshot set. An image existing in Asset Library is separate from assigning it to that version/device-size/localization. Open the file information and verify the actual pixel dimensions. Apple currently lists 2064 × 2752 or 2048 × 2732 for portrait 13-inch iPad screenshots, or the corresponding landscape dimensions. After reloading the version page, confirm that the images are still present in that set and have finished processing. Could you share the image dimensions, the selected localization, and a screenshot of the 13-inch set with any private information hidden? That would help distinguish a placement/processing issue from a validation problem. If those all match, report it to Developer Support with the app ID and exact validation message. Apple’s screenshot specifications: https://developer.apple.com/help/app-store-connect/reference/app-information/screenshot-specifications Asset Library versus Media Manager: https://developer.apple.com/help/app-store-connect/manage-app-information/manage-your-app-store-assets

“Waiting for Review” means Apple has received the submission but has not started reviewing it yet. The status alone does not tell us why it is delayed. Since you mention submitting it several times, has the current submission been waiting continuously for 17 days, or is that the total across multiple submissions? That distinction would be useful when contacting support. I would contact Apple through https://developer.apple.com/contact/ and choose the App Review / submission-status option. Include the app Apple ID, version/build, current submission date, and any existing case number. Check the App Review page in App Store Connect for messages or outstanding requests as well. If there is a critical bug fix or a time-sensitive event, Apple also has a separate expedited-review request: https://developer.apple.com/help/app-review/after-submitting-for-review/request-expedited-review/ Apple’s status definitions: https://developer.apple.com/help/app-review/after-submitting-for-review/review-status