Flutterby™! : Ah

Ah

2026-04-23 19:00:03.182364+02 by Dan Lyke 2 comments

Ah, yes, when you have to use QuickTime Player to screen record XCode to catch the stack trace before XCode shits itself...

comments in ascending chronological order (reverse):

#Comment Re: made: 2026-04-23 21:46:18.992518+02 by: markd

Let me guess, an unhandled Objective-C exception?

Had that happen doing a pairing last week, and a misuse of [NSIndexSet insertValues:atIndexes] threw an exception that made die instantly. Literally one video frame had enough partial information to figure out what's going wrong. #ilyxc

#Comment Re: made: 2026-04-24 18:52:31.588378+02 by: Dan Lyke [edit history]

Yeah, the first time was sending .length to an NSNull, the second time it passed the [obj isKindOfClass:[NSString class]] check but still blew up, so I added a [obj respondsToSelector:@selector(length)] and it worked.

(Passing stuff back and forth from Swift to Objective-C, and the Swift stuff is serializing from web requests...)