#fsck#
#
I guess Xcode still doesn't have a way to catch these errors? I load assloads of data asynchronously via operations and putting breakpoints/logging in each is not a fun task. Why can't I set a breakpoint where this error happens or force Xcode to throw an exception? This "you have an error but we're damned will not going to help you find it" attitude from Apple is so tiring.
#xcode #publishingvaluesfrombackgroundthreadsisnotallowed #fsck
[Link zum Post](https://toot.community/@chakie/114495322561753480)