Instance properties of a view is very private (adding public makes no sense) as the instance of the view is sort of temporal template which will be recreated at any time. One way, is to declare the variable independently from the view and use it in the view and other frameworks. Hard to say any details unless knowing how you want to use the variable.

Steps to reproduce the error: Create new Xcode project Open Main.storyboard Drag datepicker from the "+" Run project tap over the datepicker and scroll to 1996 I cannot reproduce the error following the steps here. Do you know what is needed?

how to go about switching the load method from local to remote, in beginner's terms? Better share your code, which causes various errors and hear from experienced programmers.

as you can see it says not nil Sorry, but I cannot see anything that is saying not nil.

What code would i use to get the data of a specific data? Is the code you are using now exactly the same as the code in your opening post?

I've seen a few postings of the same problem. Can you clarify the settings or the environment to reproduce the issue? Sort of macOS version or simulator versions or any such things may be affecting.

Is this some bug? May be, or may not be. I created a vanilla project with Xcode 12.4 of type iOS/Game/Sprite Kit. And then added LaunchScreen.storyboard with File > New > File... > User Interface/Launch Screen. I then chose the file in the pull down Launch Screen File. Whether I added an image (UIImageView) or not, the content of LaunchScreen.storyboard is shown at launch of the app. One thing I needed to care about is that without adding constraints to the UIImageView, the image was shown at an unexpected place. So, you might have done something wrong, or might have hit the edge case of some sort of bugs. Not sure under the currently shown info.

 If I go without SwiftUI, do I lose anything? With choosing Storyboard, you will see ViewController.swift or AppDelegate.swift or Main.storyboard -- all such things. will I lose any new functionality (enduser wise) by not using SwiftUI? As already said, you have never used any SwiftUI functionalities. How many of your .swift file have import SwiftUI? If you want to go with what you have learnt till now, you need to choose Storyboard. You can switch to SwiftUI and will find many functionalities are lacking in SwiftUI and many things are quite difficult in SwiftUI which was easy or not easy but you have learnt how. Please clarify one thing: Were you thinking you were using SwiftUI?

things have changed in 12.4.  Things had changed in 12.0. For instance there's no more AppDelegate.swift file. I would start at class ViewController: UIViewController before. Now there's struct ContentView: View  which I don't recall when in started learning in late 2020. Do I need to repeat? When you choose Storyboard as Interface` when creating a new project, you can find AppDelegate.swift or ViewController.swift. And then you can remove what you think is not needed for you. Is it that I never used SwiftUI? At lease in your past posts, you have never used SwiftUI.

My build is failing and I don't know why.  Swift compiler fails to output proper diagnostics when some primitive errors found in constructing views. Please use Code block (<>) when you include codes in text.

Received Failed to produce diagnostic for expression; please file a bug report What do you want? This is not a place to write a bug report. If you want some help to solve the issue, please show enough code and say so.

any password of 9 or more characters ny password of 13 or more characters Seems you want to ignore the fact that there were no description about what you had input on SIGABRT. And you expect some specific memory allocation on auto variables. Anyway, please clarify the difference between what you expect and what you actually get, for each possible inputs. Some of them may be caused by buffer overflow protections, and some other by your wrong expectations.

Error -> Left side of mutating operator isn't mutable: 'self' is immutable Please show enough code to reproduce the issue.

There was just an extra "e" OK, thank you for sharing the info. Happy to hear I could help solving your issue.

Never mind, I found that error. If you found something wrong and fixed it by yourself, please share your solution. There are some readers other than you and me, and more in the future. Sharing the solution would benefit all such readers, and me.