I have the exact same thing, I did a StackTrace on the NSLog to see where it's coming from, but I still don't have a clue: * thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.2 * frame #0: 0x00000001a2de441c Foundation`NSLog frame #1: 0x00000001057f0998 libRPAC.dylib`swizzleAPIsForHangDetection + 104 frame #2: 0x00000001057f22a0 libRPAC.dylib`initializeTrampolineBasedSwizzling + 84 frame #3: 0x000000010576e578 libRPAC.dylib`__library_initializer + 1756 frame #4: 0x00000001c7422a84 dyld`invocation function for block in dyld4::Loader::findAndRunAllInitializers(dyld4::RuntimeState&) const::$_0::operator()() const + 168 frame #5: 0x00000001c7412208 dyld`invocation function for block in dyld3::MachOAnalyzer::forEachInitializer(Diagnostics&, dyld3::MachOAnalyzer::VMAddrConverter const&, void (unsigned int) block_pointer, void const*) const + 340 frame #6: 0x00000001c74103c8 dyld`invocation function for block in dyld3::MachOFile::forEachSection(void (dyld3::MachOFile::SectionInfo const&, bool, bool&) block_pointer) const + 496 frame #7: 0x00000001c741015c dyld`dyld3::MachOFile::forEachLoadCommand(Diagnostics&, void (load_command const*, bool&) block_pointer) const + 300 frame #8: 0x00000001c741a67c dyld`dyld3::MachOFile::forEachSection(void (dyld3::MachOFile::SectionInfo const&, bool, bool&) block_pointer) const + 192 frame #9: 0x00000001c7419228 dyld`dyld3::MachOAnalyzer::forEachInitializer(Diagnostics&, dyld3::MachOAnalyzer::VMAddrConverter const&, void (unsigned int) block_pointer, void const*) const + 516 frame #10: 0x00000001c7418dac dyld`dyld4::Loader::findAndRunAllInitializers(dyld4::RuntimeState&) const + 524 frame #11: 0x00000001c743bd84 dyld`dyld4::JustInTimeLoader::runInitializers(dyld4::RuntimeState&) const + 36 frame #12: 0x00000001c74188d8 dyld`dyld4::Loader::runInitializersBottomUp(dyld4::RuntimeState&, dyld3::Array<dyld4::Loader const*>&) const + 220 frame #13: 0x00000001c741873c dyld`dyld4::Loader::runInitializersBottomUpPlusUpwardLinks(dyld4::RuntimeState&) const::$_1::operator()() const + 116 frame #14: 0x00000001c74184cc dyld`dyld4::Loader::runInitializersBottomUpPlusUpwardLinks(dyld4::RuntimeState&) const + 380 frame #15: 0x00000001c7411120 dyld`dyld4::APIs::runAllInitializersForMain() + 336 frame #16: 0x00000001c740fb98 dyld`dyld4::prepare(dyld4::APIs&, dyld3::MachOAnalyzer const*) + 3328 frame #17: 0x00000001c740eb80 dyld`start + 1724

I am seeing the same problem. This also happens in UIKit. A "long press" on the TextField reproduces the problem. Adding a UITextField inside a View is enough the reproduce the problem. I think this is a bug that Apple should address?