You're right. You may either force single pick and reopen picker immediately, removing the already selected images, until user Cancels. In case of multiple selection, how are you "sure" that user will pick them in order ? He/she could change his mind and unselect and select a new one. Which order would you consider ?

Tell us how submission concluded. Wish you it is without problem. And don't forget to close the thread after.

That may be a specific SwiftUI issue. Would you have an example which worked OK in Xcode 12 and not in Xcode 13 ? What can be done is file a bug report, not much more I fear.

When you select your project, at the very top of the file browser, and open File Inspector, what project format do you get (it is listed as Xcode x.y compatible). Could you try to set to 13.0 ? What is the answer to the last question "When you look at issues Navigator (left panel), do you get error messages ?"

When you select your project, at the very top of the file browser, and open File Inspector, what project format do you get (it is listed as Xcode x.y compatible). Could you try to set to 13.0 ? What is the answer to the last question "When you look at issues Navigator (left panel), do you get error messages ?" Can you also open the nib file as Source code (right click on the nib file in file browser and select "Open As >"

Could you post a complete code where you get the error ?     Have you defined contentData as @State var ?

What is the crash message ? I was suggesting a possible problem, if you don't care, that's OK for me, no worry. But I have nothing to check if you don't check yourself first and answer to replies.Note that the code you used dates from 2018. It is already a bit old (at the time iOS 12 or 13). There is an interesting discussion here for negative row value: https://stackoverflow.com/questions/13585220/why-is-the-row-property-of-nsindexpath-a-signed-integer.   Have a good day.

Advice to all: post bug reports.

In what you show here, I do not see the textViews ("Lorem ileum…") inside the view inside the ScrollView. That's what I would do.

OK. But are you sure the notification is sent during scroll ? Do you see "Scroll Started" printed during scroll ?

I may miss something in your intent. Do you want the notification being sent and processed during scroll, to check you don't exceed some limits ? Or do you want to send only at start of scrolling, which is what the code is apparently doing now. If the latter, you should see several print during scrolling. Is it the case ?

So the culprit seems to be in Monterey…

My question was: why don't you put directly the textViews ("Lorem ipsum…") in a view (not view controller) inside this Container View, close to what you showed in your original post ?

You have not read carefully: I moved changed in the scope of Practise. To have func outside of Practise, you need to use Environment var, not State var. See here detailed explanations: https://stackoverflow.com/questions/56718802/how-to-update-a-swiftui-view-state-from-outside-uiviewcontroller-for-example

I understand the use case. But It would be helpful to know on which line of code the crash occurs.    What about cell.initialize(withDelegate:) ?