Skip to content

Instantly share code, notes, and snippets.

@0xced
Created December 7, 2012 09:39
Show Gist options
  • Save 0xced/4232161 to your computer and use it in GitHub Desktop.
Save 0xced/4232161 to your computer and use it in GitHub Desktop.
Incomprehensible NSLog from MessageUI

This message started to appear in the console recently:

Tried to load message that we have no information about.

I have no idea what it means. Here is the stack trace with 100% Apple frameworks code.

* thread #10: tid = 0x2903, 0x0180ae31 Foundation`NSLog, stop reason = breakpoint 16.1
    frame #0: 0x0180ae31 Foundation`NSLog
    frame #1: 0x0260940d MessageUI`-[MFMessageWebProtocol startLoading] + 224
    frame #2: 0x01898367 Foundation`__31-[_NSCFURLProtocolBridge start]_block_invoke_0 + 59
    frame #3: 0x0180802a Foundation`-[NSBlockOperation main] + 137
    frame #4: 0x017d5d23 Foundation`-[__NSOperationInternal start] + 736
    frame #5: 0x017d5a34 Foundation`-[NSOperation start] + 79
    frame #6: 0x01897343 Foundation`-[_NSCFURLProtocolBridgeWithTrampoline processEventQ] + 291
    frame #7: 0x018979f2 Foundation`-[_NSCFURLProtocolBridgeWithTrampoline pushEvent:from:] + 264
    frame #8: 0x01898327 Foundation`-[_NSCFURLProtocolBridge start] + 94
    frame #9: 0x01899665 Foundation`__bridgeStart_block_invoke_0 + 33
    frame #10: 0x0189956c Foundation`_bridger + 74
    frame #11: 0x007acf99 CFNetwork`URLProtocol_Classic::_protocolInterface_startLoad(_CFCachedURLResponse const*) + 65
    frame #12: 0x007d1957 CFNetwork`___private_ScheduleOriginLoad_block_invoke_0117 + 152
    frame #13: 0x007cf8cc CFNetwork`__withExistingProtocolAsync_block_invoke_0 + 30
    frame #14: 0x00808e3a CFNetwork`___performAsync_block_invoke_068 + 25
    frame #15: 0x02f5f8fd CoreFoundation`CFArrayApplyFunction + 205
    frame #16: 0x008094bc CFNetwork`RunloopBlockContext::perform() + 120
    frame #17: 0x00809435 CFNetwork`non-virtual thunk to RunloopBlockContext::multiplexerClientPerform() + 20
    frame #18: 0x006f33a0 CFNetwork`MultiplexerSource::perform() + 276
    frame #19: 0x02f40f3f CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 15
    frame #20: 0x02f4096f CoreFoundation`__CFRunLoopDoSources0 + 239
    frame #21: 0x02f63734 CoreFoundation`__CFRunLoopRun + 964
    frame #22: 0x02f62f44 CoreFoundation`CFRunLoopRunSpecific + 276
    frame #23: 0x02f62e1b CoreFoundation`CFRunLoopRunInMode + 123
    frame #24: 0x0189febe Foundation`+[NSURLConnection(Loader) _resourceLoadLoop:] + 393
    frame #25: 0x017e80d5 Foundation`-[NSThread main] + 76
    frame #26: 0x017e8034 Foundation`__NSThread__main__ + 1304
    frame #27: 0x95443557 libsystem_c.dylib`_pthread_start + 344
@0xced
Copy link
Author

0xced commented Dec 7, 2012

It turns out this log messages happens when you run a NSURLConnection with a NSURLRequest initialized with a nil URL.

@sharplet
Copy link

Thanks for this, your comment just helped us resolve an issue we were having in our test suite!

@adamwaite
Copy link

@sharplet, what was the problem? I'm facing slow tests all of a sudden and this appears in the console.

@orta
Copy link

orta commented Apr 9, 2015

+1 - I have something in tests that isn't full stubbed out, thus it has a nil URL. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment