Ios – Could not signal service com.apple.WebKit.Networking: 113: Could not find specified service

From your description I suspect the most likely explanation is that you have some error in your memory management. You said you've been working on iPhone development for a few weeks, but not whether you are experienced with Objective C in general. If you've come from another background it can take a little while before you really internalise the memory management rules - unless you make a big point of it.

Remember, anything you get from an allocation function (usually the static alloc method, but there are a few others), or a copy method, you own the memory too and must release it when you are done.

But if you get something back from just about anything else including factory methods (e.g. [NSString stringWithFormat]) then you'll have an autorelease reference, which means it could be released at some time in the future by other code - so it is vital that if you need to keep it around beyond the immediate function that you retain it. If you don't, the memory may remain allocated while you are using it, or be released but coincidentally still valid, during your emulator testing, but is more likely to be released and show up as bad access errors when running on the device.

The best way to track these things down, and a good idea anyway (even if there are no apparent problems) is to run the app in the Instruments tool, especially with the Leaks option.

Here's what I'm doing:

1) In my framework CMakeLists.txt file, I have the following:

IF (APPLE)
       SET_TARGET_PROPERTIES( MyFramework PROPERTIES FRAMEWORK true)
       SET_TARGET_PROPERTIES( MyFramework PROPERTIES
           XCODE_ATTRIBUTE_INSTALL_PATH @executable_path/../Frameworks/  )
ENDIF (APPLE)

The second "set_target_properties" line configures the framework to always be looked for in the application bundle in the Frameworks sub-folder.

2) In my top-level CMakeLists.txt file, I add setup a unified binary output directory:

SET (CMAKE_LIBRARY_OUTPUT_DIRECTORY ${PROJECT_BINARY_DIR}/Bin)
SET (CMAKE_RUNTIME_OUTPUT_DIRECTORY ${PROJECT_BINARY_DIR}/Bin )
SET (CMAKE_ARCHIVE_OUTPUT_DIRECTORY ${PROJECT_BINARY_DIR}/Bin )

3) Then, in my applications' CMakeLists.txt file, I have the following:

IF (APPLE)
       ADD_CUSTOM_COMMAND(
               TARGET MyApp
               POST_BUILD
               COMMAND ${PYTHON_EXECUTABLE}
               ARGS ${CMAKE_HOME_DIRECTORY}/CopyFramework.py
               --binary ${PROJECT_BINARY_DIR}/Bin
               --framework MyFramework.framework
               --app MyApp.app

    )
ENDIF (APPLE)

This calls out to my python script, which does the work of assembling the src and dest paths, and actually copying the Framework.

The final trick is that since this is a Mac only thing, I can rely on an Xcode environment variable within the Python script:

           config= os.environ["CONFIGURATION"]

This allows me to assemble the complete path to the actual binary locations of the framework and the app.

The one thing I wish was that there was a CMake variable that would expand to the current Config within the context of the ADD_CUSTOM_COMMAND... It'd be nice to not have to resort to using the Xcode environment variable.