First, did you try an option-clean build folder ? You have some hints : Failed to update scene 'aiS-Tf-QFZ, sJh-qB-mKz, O4N-O0-MPJ, and jsw-BD-Vbk' You should search for the Objects ID (as aiS-Tf-QFZ) and see if you see anything wrong. Maybe you could post the XML code for those objects ?

Could you explain precisely what the problem is ? Do you get an error message ? Where exactly ?

I have an example of app on the appstore that exists in 2 versions, normal and Pro, at different price. After rejection (considered as spam), I had to explain in detail how the versions where different, with different functionalities, even though the core of apps was common In your case, the single app could be limited in number of registered accounts or individual preferences, unlimited in the other. You should consider as well additional features. In addition, in the app information, you should make it clear that 2 versions exist. adding special features in the future, but for now it is exactly the same. That's risky. My advice (but that does not guarantee it will be OK!, just a personal opinion) would be to add a few new features immediately, and make things very clear for reviewer when you submit any of the apps or their updates.

Have you checked the setting in both: Project iOS deployment target Targets Deployment info May be one is set at 14.3 but the other 14.0

If you create programmatically, you need to define the frame or create constraints to position correctly the label in view. But I do prefer using IB. Much simpler and it lets other understand what the UI design is. A big plus when working in team.

Did you try declaring the NSSlider as strong (remove weak) ?

So, implement your own DatePicker. The link I provided will give you useful hints.

Thanks for feed back. Not sure it is a bug, but this is very subtle and not described (or at least could not find the doc). Could file a bug against documentation at least.

Does it behaves so only in your app ? Or also in other apps ? If only in your app, you should give more details and show relevant code.

I am pretty sure it will work without a xib. xib solution must work, but you need to manage topLevelObjects. Which is not totally immediate…

What alignment are you exactly looking for ? Center to what ? To center in its frame: Image("Sacropped_image") .resizable() .scaledToFit() .frame(width: 240, height: 250, alignment: .center) .border(Color.red, width: 4)

I have tried to use your code. Could not figure out how to use ut. And could not crash it either. Could you show the exact and complete crash log ? I would not be surprised that index out of range is value 0 (which means voti2 is an empty array). But your code is surprising. I see nowhere any item appended to voti2. For sure, voti2 set to tutto() But func tutto() - [Float] { returns voti2 without appending any element. So, when you write voti2 = tutto(), you copy voti2 into voti2 …

Could you show the code you have tried, with a state var for each list ?

That will avoid the crash. But the real point is to check if voti2.count is ever more than zero. If not, that confirms there is a design flaw. This is what must be corrected. Note: in anycase, it is a effectively good practice to check index values are within bounds. A very simple extension may even simplify writing extension Array { func isValidIndex(_ index: Int) - Bool { return index = 0 && index self.count } } Then if(mediaEffettiva mediaFloat && voti2.count = con+1 && con = 0) { voti2[con] += 0.5 } becomes a bit shorter if mediaEffettiva mediaFloat && voti2.isValidIndex(con) { voti2[con] += 0.5 }

Could you show the code where you add layer to tableView cell ?