smb big sur

For months now we're trying to find an issue with one of our apps, were a window suddenly becomes narrow and can't be resized horizontally any more. It's a bug that only happens sporadically and we can't provide a focused test project to demonstrate the issue; thus we can't ask for code-level support at this moment. To debug this issue, we've overwritten a private method on NSWindow that gets the constrained window min and max sizes (valuable hint of Kristin from the AppKit team in a WWDC 2025 one-on-one session where I was able to show it to her in my debugger). When the bug hits, the maxSize's width (usually 10000) becomes smaller than the minSize's width. One way (but not the only one) to trigger this issue is to move the window from one display to another and back. Sometimes the bug triggers after a few back-and-forth movements, sometimes it takes minutes to trigger or I give up… but for other people the bug happens seemingly out of nowhere (of course there must be a trigger but we haven't noticed common

Hi all, I’ve run into a signing/entitlements problem that shows up only on Big Sur (11.x). The very same .app launches perfectly on Monterey (12), Ventura (13), Sonoma (14 / 14.5) and Sequoia (15). Failure on macOS 11 com.apple.xpc.launchd[1] (application.app.myapp.exams.566312.566318[1602]): removing service since it exited with consistent failure – OS_REASON_CODESIGNING | When validating …/MyAppNameBlurred 3.13.1.app/Contents/MacOS/MyAppNameBlurred 3.13.1: Code has restricted entitlements, but the validation of its code signature failed. Unsatisfied Entitlements: Binary is improperly signed. Launching from Terminal: open -a /Users/admin/Downloads/MyAppNameBlurred 3.13.1.app kLSNoLaunchPermissionErr (-10826) | Launchd job spawn failed with error: 153 What I’ve already checked # signature itself codesign -dvvv /Users/admin/Downloads/MyAppNameBlurred 3.13.1.app # => valid, Authority = Developer ID Application, runtime enabled # full deep/strict verification codesign --verify --deep --stric

If I control-click (or right-click) on a view, there is no longer an option to extract to subview. I also looked under the refactor option that comes up and it's not there either. Was this intentional? If so, is there an easy method to extract to a subview like in earlier versions of Xcode? Also, if I control click on a view and the context menu comes up, there used to be different embed options (ZStack, HStack, etc) now there's only embed. Not a big issue because you can just change Container to whatever.

When I startAdvertising, my localName is long，Will not be truncated and the type is 0X09; self.advertisementData = @{CBAdvertisementDataLocalNameKey: localDevName, CBAdvertisementDataServiceUUIDsKey: @[[CBUUID UUIDWithString:serviceUUID]] }; [self.peripheralManager startAdvertising:self.advertisementData]; IOS 18.5: The service uuids in ADV_IND occupies 24 bytes, the local name in SCAN_RESP is 20 bytes in size and has not been truncated, and there is no manufacturer specific data in SCAN_RESP;You can view the following image： But in IOS26, why is the local name truncated to only 6 bytes for the same message, and why does SCAN_RESP always contain Manufacturer Specific Data; Why is there such a big difference, and what changes has iOS 26 made for broadcasting? Is it necessary to include Manufacturer Specific Data in the IOS 26 SCAN.RESP message? What documents are available for reference? Is there any way to ensure that the local name is not truncated? Is there a maximum length limit Are there other wa

New features in WatchOS 26 with configurable widgets make it more important than ever that apps adopt IntentConfiguration options where applicable. I develop an app with an Apple Watch complication/widget on many many user's Watch faces around the world. I've completed updating my code to support WidgetKit and remove ClockKit. However, I face huge issues adding support for users to configure their widget/complications. If I update a widget to go from StaticConfiguration to IntentConfiguration, even when keeping the kind string the same, the widget disappears from the Watch face. This is an unacceptable user experience meaning I can't proceed with the migration. The problem is users will expect me to offer configuration in the Watch face soon for their widget/complication. Currently this process is done in a sub-optimal way in the app itself. A similar issue exists on iOS where the widget will just freeze indefinitely is migrated. This issue still occurs on the iOS 26 and WatchOS 26 betas. So how to move this

So game I created a racing game with open world , all content was made by me from scratch , I understand the appstore was flooded by racing games like mine , but if u compare , test and etc it has been much better , when I started to develop this game , I think about quallity and good experience for users because I've seen what a trash games on the appstore , with screenshots from gta 5 and the game by itself is really just an asset , I aldo bought an asset , but I modified amd added an half of things in this car physics asset , more than half of this asset modified , I'm worked on this game about 4 years , I have big plans for this to update and work more to give to users a console like physics and experience , right now I tried to add some features to my game and adding online mode , the main idea of The game was an open world racing game like forza horizon , with similar car physics , tuning system , and in feature updates with online races , rankings and etc , so what to do right now idk , just t