I am experiencing the same behaviour with TextFields. I'm also facing non-responsive Buttons, if lazily-loaded otherwise conditionally created. I don't have a solution, but it's interesting that you reported this two weeks ago, as that is when I first hit this problem. Up to that point, I was totally confident in Mac Catalyst as a platform. Now, I'm wondering if I need to abandon it. I am wondering if it was a change in Xcode SDK or Big Sur update. The iOS build is 100% stable. My Mac Catalyst build was fine for 2 months, then something changed - either my code or environment - such that I can no longer ship it.

Apple now allows you to use a single bundle ID for Mac and iOS apps through Universal Purchase: Universal Purchase for Mac Apps Now Available The macOS version of your app can now be included in a universal purchase, allowing customers to enjoy your app and in‑app purchases across iOS, iPadOS, macOS, watchOS, and tvOS by purchasing only once. Get started by using a single bundle ID for your apps in Xcode and setting up your app record for universal purchase in App Store Connect. https://developer.apple.com/news/?id=03232020b Offering Universal Purchase Upload your apps to the app record using a single bundle ID. While the bundle ID must match the bundle ID you enter in App Store Connect, the apps can have different version numbers and build strings. https://developer.apple.com/support/universal-purchase/

Thanks @lucienkerlWIT, that worked for me also. So strange it isn't required for debug builds.

I'm hitting the same issue (no body allowed with GET) in Swift with URLSession. The URLSession throws an error when it finds a body length for the GET message. It's maddening that one team's viewpoint on the use of the GET verb is codified on the client end, so that it blocks compatibility with so many existing APIs.

FYI on the arm64 (M1) Macs, Homebrew installs to /opt/homebrew/bin.