Sorry, I should have noted one important thing. I have not explored the open source part of Swift nor could not have used any debugging features. So, the part describing the current behavior is nothing more than just my guess. It may be caused by some bugs of the current implementation, you can send a bug report to swift.org .

Thanks for sharing what you have explored!

Sorry, my answer was too late. I could not see the latest answer at the time I clicked Submit.

Thanks. Then you have something special in the hidden parts of your project. Please show all the things to reproduce the issue.

Better start your own thread including the code which explains what you have tried till now.

I do not understand what you want to say. If you can make it work with your own way, please do it. Please share your code when done. Good luck.

@mmklug, Thanks for pointing it out. But I cannot find any other workaround till now. If you find one, please share it.

We need to guess what are AccountBackEnd and PublishedClassAccount. (Please show enough code when asking. > @tylerlw82) But according the other parts of your code, they seem to be ObservableObjects -- reference type. In almost all cases, using @Published would not work as you expect when used with reference types. You need to modify far more parts than shown in this answer.

am I doing any of this right? Right or wrong depends on the context. If you use them as @StateObject or @ObservedObject in a View, it may be right. But using them as an @Published property or somewhere else than a View, it is very likely to be wrong.

Please do not include two or more topic in a single thread. When you have a new question, you should start a new thread. (Even when many parts of them are related.)

Happy to hear you have solved your issue. But unfortunately, storyboard connections may be corrupted or lost by various means, so hard to say what have caused this issue in your case. Anyway, you have learnt where to check and you can go on learning iOS development when another similar issue occurs.

@ShinehahGnolaum, I'm not sure why anyone would fetch just the unified contacts. You may be misinterpreting what unified contacts mean. Better take enough time before marking an answer as SOLVED, you cannot unmark it. And as the editing feature is very limited in the dev forums, you may need to use Your Answer when showing some code.

Thanks for showing the additional info. But please remember you have just mentioned the combobox, but not that it was in the Create a new simulator window. Anyway, I have no clue as for now, it may be a problem of macOS Monterey 12.0.1 (I'm using Big Sur), or there may be something special which you have not mentioned yet.

Hard to say whether it is good or not. Many developers are still suffering to explore what would be the best practices in SwiftUI.

you should better show more context (especially your code), to get better responses sooner Why don't you show your code enough to reproduce your issue? A few screen shots and very little explanation would not be appealing to many readers.