An EXC_BAD_ACCESS is happening because you're trying to access a resource that no longer exists, so it looks like something in your code is trying to do 'something' with that window after you've told it to be released when it's closed. You need to debug your code and ensure you're not trying to do anything with released resources.

What platform versions are you running this on? What version of iOS? What version of macOS? What version of Xcode? And, how wide is the window that you took the Second View screenshot of? Does the back arrow (or the title) appear in the right location if the window is wider? What happens if you resize the macOS window while it's running? Do the arrow and title draw correctly?

Wrong place. These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. This isn't the place to advertise your wares.

What conversation? Could you maybe just give us an example of what you're talking about? Give us some code and explain what the issue is and what the current workaround is. If you believe it's a bug, why not just raise it? https://feedbackassistant.apple.com/ then post the FB number here.

Not sure if this is the problem, but you're passing by reference that error variable into that call, but you've set it to nil, so if there's an error in that call it can't write that error to that variable because it's nil. Try: NSError *error; instead. Then, when inspecting the results of that call, you need to check if error is nil before trying to access its contents.

Does it matter? You can use true, TRUE, YES and yes, can't you? Besides, saying something is 'true' makes more sense in a sentence describing the effect of some function, rather than 'yes'. a BOOL used to be YES or NO for the last quarter of a century It's still YES or NO. If I'm writing ObjC I use YES/NO. If I'm writing Swift I use true/false. I think it's personal preference at this point.

Please don't post screenshots of text errors. They aren't searchable, so if someone else has this same error they won't get to this page where we might have a solution... Okay? Now, what have you tried? Have you updated your project's settings? Xcode will recommend you update them when you load the project. Have you cleaned the project? Deleted DerivedData, etc.?

Please don't make duplicate posts, especially just to add a newline at the top...

Is this in an app you're developing? If not, you're in the wrong place. These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. Product support questions can be asked over at the Apple Support Forums. However, there's a little icon there with an eye and a line over it. Tap that, and it should mask your password. This is standard across most password entry fields. If I've misunderstood your issue, please reword it.

Do you need those Spacer()s in the HStacks?

What does your app description say in its entirety? Give us the entire text so we can see what they're talking about. It might be that you're mentioning things available in the app, but it's not clear that everything requires a subscription. Your UI also says, in grey text - which isn't immediately obvious: "A subscription is required to use VentWell and access all features." This suggests to me that some features don't require a subscription? Not sure why you have that big "Monthly" button with the text saying, "3 days free, then $9.99/month" and immediately below it is the same text in grey. Any reason that needs to be there twice (plus the grey text at the top saying it in a slightly different way)? On a separate note, does your description really say "Subscription begins after 3 day free-trial and auto reknews monthly"? If so, that's not how you spell "renews".

I think this is one of those 'helpful' things because Xcode doesn't want you to miss out the trailing quote for a String, etc. I can't find any option to turn it off in either Xcode's settings, or System Settings > Keyboard. And there's nothing in right-click substitutions (they all seem disabled). I recommend you raise a suggestion in the normal way and ask that they include some way of not doing this in files with certain extensions. If you look in Xcode's settings > General tab, this is the sort of thing I mean, and it would include: md, txt, xml...: Your bug/suggestion won't really get progressed if it's only posted in these Developer Forums. Raise it at https://feedbackassistant.apple.com/ You can then post the FB number here if you want.

You should probably raise this as a bug in the usual way. It won't really get progressed if it's only posted in these Developer Forums. You need to raise each issue you find separately at https://feedbackassistant.apple.com/ You can post the FB numbers here if you want, so that others can link to them.

Is this your own app? If so, debug it. If it's someone else's app, is it one specific app? If so, tell that developer directly. You can leave them a review on the App Store, or their website. If it's multiple apps, then raise a bug at https://feedbackassistant.apple.com/ and post the FB number here.

Have you followed everything on this page? https://developer.apple.com/documentation/uikit/adding-a-custom-font-to-your-app