Can you clarify what you mean by user has not sharing location? Do you mean any sort of permissions or authorizations about location? Or your app has a Share Location button and you want to check if user has tapped it or not?

What version of Xcode are you using? Which model of simulators? Of which version of iOS? You may need to clarify all such things when you find something weird.

Can you share how you have set up the constraints of UIImageView, and the result both of Xcode 12 and 13? Showing some screen shots would be preferable.

One thing clear is that your predicate does not satisfy the requirement documented. Maybe you have some experiences implementing functions like min and max, and your mind is bound to such experiences. Free yourself from experiences, any frameworks or libraries might not work as you experienced.

@jkspiezio, thanks for clarifying. Can you try creating a project which can reproduce the issue, but not using Firebase thing? Unless your code is doing something obviously wrong (and in this case, it is not), it is hard to say something sure with just seeing the code. By the way, you should better show your latest code, as editing old post is quite limited, you may need to use Your Answer to show some updates to your question.

I know many developers are suffering this UIButton issue. Have you sent a feedback to Apple?

@AnimalOnDrums, I am using the latest version of Xcode Are you sure you are using Xcode 13.1? Xcode 13.0 does not contain macOS SDK 12.

Can you show what you think is the RIGHT answer?

Even created a new objective-c app and migrated the code needed to interact. Do you say that your newly created Objective-C app cannot get data from iCloud documents? Then it is not a problem of migrating Swift. And as iCloud Documents is in a process of closing, it is reasonable new apps would not be able to use it.

Generally, you should better think that embedding a NavigationView inside TabView is not supported. Better start a lot of additional work now. Or, if you expect some readers would be able to solve your issue, you can start your own thread.

Will it really help if I post more code? > In many cases, especially to readers who want to run the code and see what is happening, it is more appealing. The feedback assistant is a little black holeish. > The responses to feedback is far from satisfactory, and sharing some bug info may be useful for many developers, but the right way to push Apple to fix bugs is writing feedbacks.

What is a Standard position? > It is shown as a guiding line. Are there any docs on this new 'feature'? > No, take this as an as-far-as-I-tried thing.

People who has done a tutorial recently would rarely try to write an answer on Q&A sites. Please show enough code to appeal to readers who can say something.

Thanks for trying and sharing the new code. But I cannot find any critical issues with a glance. But, anyway, if your newly built Objective-C app runs as expected, your Swift version of the app should also work (if you correctly implement all things in your Objective-C code), even though NSPersistentStoreUbiquitousContentNameKey was deprecated long ago. Have you checked all the ids and the names are the same in Objective-C project and Swift project?

Not many readers would like to go deep into external links. You should better show any of your codes as text as far as you can.