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.

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

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 >"

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 ?"

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.

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

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 ?

There are several posts that show there is a problem with draw in iOS 15.    Such as this one where an image is repeated:    https://developer.apple.com/forums/thread/691431?answerId=689899022#689899022     You should file a bug report.

Could you post your exact code ?

OK, so I understand this is not a runtime issue, more a wrong diagnostic from Xcode ? Which is worth a bug report but less a problem for development. Could you paste a screenshot with the error ?

Did you try to use this color elsewhere ? In a place where some color works, change to this color immediately after. Does it crash then ? What I don't understand: if print is not called, that means the crash is not there ? Or do I miss something ?

Sure, but there may be some issue elsewhere, so it is always better to test the same code. But I understand you cannot show this code. So, wish you good continuation.

Sorry it didn't help. It seems they have made a lot of changes in navigation bars causing some regressions. Did you file a bug report ? Just to check, could you copy the exact same code in RootVC from SecondVC ? Where do you call those codes ? Could you try in viewWillAppear ?

Thanks, but we miss a lot of code to be able to test.