On Sep 6, 2018, at 2:03 PM, Jon Gotow <gotow@...> wrote:
Hmph - now that you mention it, there's no current runloop at that point - the app is still launching. So [NSRunloop currentRunLoop] is probably returning nil. You could grabbing mainRunLoop and running that, but I don't know what impact that's going to have during the app launch process.
I wondered about that myself, and logged out the values of [NSRunloop currentRunLoop] and [NSRunloop mainRunLoop]. They showed the same non-nil value.