cdfinder,
@cdfinder@techhub.social avatar

Wow, #Xcode 15.3 and #macOS 14.4.1 are such a weird dumpster fire of strange bugs and problems.

Merging the AppKit and UIKit low-level system frameworks is not going all too well, obviously.

That error message in Xcode is catastrophically ridiculous, really.

It indicates yet another serious bug in Apples own private frameworks.

Sigh.

i2h3,
@i2h3@toot.community avatar

@cdfinder "Merging the AppKit and UIKit low-level system frameworks is not going all too well, obviously." Where can I read more about that? Apparently, I missed out.

cdfinder,
@cdfinder@techhub.social avatar

@i2h3

The massive problem is that this is of course NOT officially documented by Apple.

We have just seen that from numerous crash reports, "hang" reports, and also when setting breakpoints in system callback methods, and checking the callback stack. More often than not we see the "UIKit.framework" playing a great role in macOS applications, especially when there are problems..

And not only is that not documented, it also causes massive amounts of problems, when the behaviour of the long established AppKit frameworks suddenly changes, and you have no idea where to start looking.

Essentially, after each new major yearly macOS release, we should test EVERY SINGLE system call, which of course is not really realistic.

This is very bad for the overall stability of macOS itself, and all the Mac applications.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • macos
  • DreamBathrooms
  • everett
  • InstantRegret
  • magazineikmin
  • thenastyranch
  • rosin
  • GTA5RPClips
  • Durango
  • Youngstown
  • slotface
  • khanakhh
  • kavyap
  • ngwrru68w68
  • ethstaker
  • JUstTest
  • osvaldo12
  • tester
  • cubers
  • cisconetworking
  • mdbf
  • tacticalgear
  • modclub
  • Leos
  • anitta
  • normalnudes
  • megavids
  • provamag3
  • lostlight
  • All magazines