11.3 GB is the compressed file to download. But you will need an extra 15-20 GB at least to uncompress. Plus a lot of GB to install. All in all, you should have at least 50 to 80 GB available to install new version. That's a lot effectively. You could try to download from here: https://developer.apple.com/download/more/ It requires usually a little less disk space.

I cannot access the screenshot. It would be much better to show the code itself. I have a class called guessingBar guessingBar is the class of guessBar ? If so, you should name it starting with uppercase: GuessingBar guessingBar which holds 6 guessSlots So guessSlots is an Array, of what ? Or do you have 6 different guessSlots vars (guessSlots1, guessSlots2…) myGV is a structure what is the name of the struct ? Should be MyGV myGV is an instance of the struct ? Exact ? var myGV : MyGV How did you initialise it ? So, there is too much guessing here, please make it clear. I expected to be able to read the array Tell what error you get

You can check status : https://www.apple.com/support/systemstatus/ and here https://developer.apple.com/system-status/ At this time, everything seems OK. Are you going through a firewall ? Ofr with a slow connection ?

That's logical. As you had defined some constraints (top and bottom, may be leading as well ?), you need to define constraints for all directions, as I told in previous post.

Have you looked in the faces gallery whether you could find it back ? https://support.apple.com/en-gb/guide/watch/apdd909455f0/watchos Here is the list of available faces in WatchOS 7 https://support.apple.com/en-gb/guide/watch/apdd909455f0/watchos But they do not say if they changed something in 7.5. Is the one you speak about the Infographie (which is my favorite as well) ? If you don't find it, I suggest to file a bug report. A detail: it is WatchOS 7.5, not iOS 7.5.

We miss elements to test: What is DrawShape ? what are data ? Could you tell very precisely what is not aligned ?

To handle a notification, you have to: register to this notification (in general in viewDidLoad), by adding an observer NotificationCenter.default.addObserver(self, selector: #selector(someFunc), name:.kNotif, object: nil) // you need to know the name of notification The name is defined by the one who post it (here Firebase), in general as extension Notification.Name {  public static let kNotif = Notification.Name("someName") } You define the func as:     @objc func someFunc() {      // Do what you need here }

Could you explain the use case and the problem ? You have a VC1 displayed. From there, you will segue to another VC2 (via a button ? Automatically ?) If so, perform is called from VC1, not in viewDidLoad, nor ViewDidAppear (users need to have time to see VC1), but from the IBAction. But the vc containing this method should remain in the stack.  This depends on the type of segue. But are you sure you don't want a navigationView here ? Have a look here: https://stackoverflow.com/questions/25966215/whats-the-difference-between-all-the-selection-segues So, please explain use case.

_how the collaboration works _ Could you explain your question ? Which collaboration ?

Finally, we can have images in the forum. That's a GREAT plus. Yes, you can define different VC for each object. You can also: create the objects in IB: there are several TableViews, several Collection views Some may be a subclass of UITableView, UICollectionView, … If needed, create Views in IB, to embed some elements which are logically linked connect each object to its IBOutlet

How would have this password request helped you get your iPhone back ?

That's a great new release ! Capability to add comments will help keep the thread cleaner, not mixing comments, like this, to answers. Congrats.

Until the battery is empty… And in the meantime, if they hide in a metallic enclosure, you'll get no signal anyway.

Have you tried all the solutions described in the other thread ?

You have pretty good Apple tutorials for SwiftUI. Not at the level of Develop in Swift, but good enough. https://developer.apple.com/tutorials/swiftui I was wondering if it's worth learning UIKit first as given in the book, or is it better to wait for an updated SwiftUI version book, and skip learning UIKit entirely? SwiftUI has a lot of constraints, and I personally find it quite inflexible (in many cases, you have to find workarounds to achieve what you could do simply do with UIKit). So, answer is a big NO: Swift + UIKit are not obsolete and won't be obsolete any time soon.