so we've pulled the version, made the adjustments, kept the same build, and resubmitted it My experience is that it is better not to pull the version but simply push a new version with a new build.

Did you explain in the note to reviewer all you did (as explained in your post) to satisfy the requirements ? Only remaining point it seems is the 24 hours requirement. How do you handle it ?

Seems to be a known issue. See this, they say they have a fix: https://www.youtube.com/watch?v=1uVb8haTdeo

Somehow similar issue occurred to me some time ago when trying to reply. Reply did not show, no error message but reply was registered. Leading to duplicate posts as I retried. https://developer.apple.com/forums/thread/779778

Welcome to the forum. That's more a question for the support forum: https://discussions.apple.com/welcome Or possibly a bug report: https://feedbackassistant.apple.com

If I understand your question, this conversion depends on screen resolution. points = pixels / scale factor scale factor is usually 2 or may be 3. It was 1 in older iPhones (iPhone 3 and below) or iPad; See table here: https://www.ios-resolution.com But why not using only points ? Why do you need to use pixels ?

I think this should help, at least for creating the hierarchical table: https://levelup.gitconnected.com/swiftui-hierarchical-table-2-ways-c5b734438e17

Great feedback. One question: _dismiss is changed - for some reason - in ItemsListView, which causes the view to redraw, causing the List to redraw, causing every ItemRow to redraw, causing the confirmation dialog to disappear because the row it was attached to no longer exists. changed from what to what ?

I probably miss something. Why do you compile with Xcode 16 and not directly Xcode 26, as you have added a class defined in Xcode 26 ? Did you set an OS target somewhere ? (__IPHONE_OS_VERSION_MAX_ALLOWED) Please show the code where error occurs.

Welcome to the forum. Could you show what is in the build section (in the first screen shot, it is hidden by the add build window). Normally, you should see your build there.

I sympathise with you. 🥲 SwiftUI may be great in some aspects, but I often find that fine tuning to achieve a precise UI behaviour is a nightmare. When it is impossible to understand why SwiftUI reacts in a certain way, you end up spending enormous time just to turn around SwiftUI to mimic UIKit behaviour. Big sigh.

Why does SwiftUI think the data is different? Maybe it's not that it evaluates data has changed but just that it needs redraw (even only for dark mode switch). But I'm not expert enough in SwiftUI to be sure. That's an issue I find with SwiftUI, understanding and possibly controlling what it is doing in the back or find a workaround. I'm still much more comfortable with UIKit.

If that may help, I found this, but did not test, using ScrollViewReader, but you've probably found as well: Get the scroll position: https://stackoverflow.com/questions/62588015/get-the-current-scroll-position-of-a-swiftui-scrollview Set the scroll position (in .onAppear ?): https://www.hackingwithswift.com/quick-start/swiftui/how-to-scroll-to-a-specific-row-in-a-list Or would it be enough to set the selection when it exists ? https://stackoverflow.com/questions/74365665/force-deselection-of-row-in-swiftui-list-view/74368833#74368833

Did you try a clean build folder. In my case, it cleared a lot of errors.

Is there an easier way to get these imports to get automatically added when I select a type using Ctrl+Space? I don't think so; you probably have to add it at the right place. You can file a report asking for improvement.