I finally started implementing dark mode in my Mac apps. Since I myself am one of those who can't stand the dark mode, I didn't have any personal incentives to implement it. I do hear that many users like dark mode. And my apps are used by thousands of people. However, ever since dark mode was implemented on Mojave I received exactly 1 (one) request to implement it. So naturally it was never a high priority. I do believe that apps should support dark mode. Just wanted to share the actual feedback I received from users.

That's great!! Thanks for putting it together. I thought of creating my own replacement, but your project seems to do exactly what I need (as well as any other Mac developer, in my view). The redesigned NSAlert on Big Sur is a total disaster. In addition to cutting off long messages, the center-aligned text is simply not suitable for human consumption. The entire centered alignment of elements is also tasteless and visually unappealing. Those who designed the alerts lack the very basic knowledge of text legibility as well as human-oriented UI design in general. It's a big embarrassment for Apple. They're supposed to have the best UI designers in the world. And yet it looks like Apple just grabs random people from the street to design certain UI elements. Sadly, despite overwhelmingly negative feedback from both users and developers, nothing was changed on Monterey. I hope to implement NSCustomAlert in all my apps as soon as possible. And hope that other developers will follow the suit. P.S. In your current code, the alert cannot be moved with the mouse. I solved this issue by removing the NSWindowStyleMaskDocModalWindow mask AND adding _panel.movableByWindowBackground = YES. I'll post this feedback on git as well.

Absolutely. While Apple did introduce some nice UI refinements on Big Sur, there are also several UI changes that are quite horrible and defy any common sense and basic rules of intuitive human-oriented UI design. Unfortunately, Apple didn't improve anything on Monterey. I'll soon submit several messages dedicated to each of the unfortunate UI changes on Big Sur.

yes, same issue here. it's a huge bug in Xcode 13. there was no issue in beta 1. the problem started from beta 4. i thought it was fixed in the final release as it worked normally for a few hours. but now the same problem came back I'm re-submitting this bug to Apple. in the meantime, I'm back to working in Xcode 13 Beta 1 as there's no issue there.

I received a reply from Apple where they ask to check the forthcoming new update Xcode 13.2 RC: https://developer.apple.com/download/ I've been using it for two days and so far it looks like the issue is fixed there.

@coderkid: i wonder if you have the same issue with Xcode 13.2 as it fixed this for me. although i never had this issue before Xcode 13.

Important correction: This problem only happens on macOS Ventura (latest beta). There's no issue on macOS 12.6.

@Ptit-Xav: I just added a correction: The problem only happens on macOS Ventura (latest beta), no issues on macOS 12.6.

Ha. I installed Ventura on a different partition of the same MacBook Pro (M1 Pro, 16", 2021) - and outlets work in Xcode 14 there with no issues. It means to me that the bug is somewhere there hiding, waiting for the right conditions to happen. But, hopefully, it must be extremely rare.

You can create promo codes in Services > Promo Codes.

I can confirm that Info.plist management is totally screwed in Xcode 14. While I didn't seem to have issues in the Target Properties section, the Document Types section is simply dysfunctional. I submitted bugs to Apple.

Yes, I have an app that's using SMTP services in Mac App Store.

to answer your subject question: NO

no. yes.

@mgrushin: Thanks!! It did work. I'm still not sure what it's all about... Mac apps don't require any provisioning profiles. I don't have any provisioning profiles specified. But now I see that indeed a provisioning profile is generated in ~/Library/MobileDevice/Provisioning Profiles upon submission of the app to Mac App Store. The directory is also named MobileDevice while, once again, it's not a mobile app - but I guess that's how it works. Thanks again! Leo