{"id":252,"date":"2006-11-24T17:55:56","date_gmt":"2006-11-24T21:55:56","guid":{"rendered":"http:\/\/auroralux.net\/blog\/2006\/11\/24\/closing-the-loop-on-core-recipes\/"},"modified":"2006-11-24T17:55:56","modified_gmt":"2006-11-24T21:55:56","slug":"closing-the-loop-on-core-recipes","status":"publish","type":"post","link":"https:\/\/fhmiv.net\/blog\/2006\/11\/24\/closing-the-loop-on-core-recipes\/","title":{"rendered":"Closing the loop on Core Recipes"},"content":{"rendered":"

A while back, I had some problems<\/a> with Apple’s Core Data ‘Core Recipes’ example. <\/p>\n

I couldn’t find anything on Google, so I emailed a friend of a friend at Apple, and ended up getting some VERY helpful troubleshooting tips from Matthew Firlik. I asked if I could post them and he said yes, so here we go: <\/p>\n

\n However, I have seen these symptoms in the past when
\nthere was an incongruity between two settings — the “Product Name”
\nand the CFBundleExecutable for the application. (These values should
\nbe the same, otherwise the Finder gets rather confused.)<\/p>\n

Try this:<\/p>\n

– Open the CoreRecipes project, and expand the “Targets” group
\n – Double-click on the “CoreRecipesApp” target to bring up the target
\ninspector
\n – Enter “Product Name” in the search field to find the build setting<\/p>\n

The value should be “CoreRecipes”. Now, if you click on the
\n“Properties” tab in the inspector, the executable will also be listed
\nin the topmost text field — and it should match (“CoreRecipes”). For
\ngood measure, click the “Open Info.plist as File” button at the bottom
\nof that pane, and inspect the file — you should find the values in
\nthe file as well:<\/p>\n

CFBundleExecutable<\/key>
\n CoreRecipes<\/string><\/p>\n

If you build the application, and then go to the Finder and “Show
\nPackage Contents”, you should be able to ensure the information
\nmatches. The values in the “Info.plist” in the Contents directory
\nshould match name of the executable in the Contents\/MacOS directory.
\nA good thing to do is to drag the Info.plist from the build product
\nonto the Xcode icon (to open it), and then under the “Format” menu
\nselect “Parse as Property List” — that’ll ensure it’s a valid format.<\/p>\n

– – – – –<\/p>\n

Now, more recent project templates don’t actually put the executable
\nname into the Info.plist — at least, not directly. They actually put
\nin:<\/p>\n

CFBundleExecutable<\/key>
\n ${EXECUTABLE_NAME}<\/string><\/p>\n

and then check the “Expand Build Settings in Info.plist” checkbox in
\nthe build settings for the target. This tells Xcode to process the
\nInfo.plist file at build time and put the correct information into the
\nproperty list. If the above didn’t show anything obvious, you might
\ntry changing the setting in the Info.plist and checking the build
\nsetting, to see if that might help.<\/p>\n

– – – – –<\/p>\n

If things still aren’t working, then a couple of other things to try:<\/p>\n

– If you build the application, and then run from the Finder (double-
\nclick) rather than from Xcode, does it work correctly?
\n – Does a basic Core Data application (built from the stock template
\nin Xcode) exhibit the same problem?
\n – If you open the build settings for the application target, is the
\n“ZeroLink” option enabled? And if so, do things work if you turn it
\noff?
\n – If you change the store type in the -setupDefaultStore method in
\nthe AppDelegate class to NSSQLiteStoreType (rather than the XML
\nstore), does it work?\n<\/p><\/blockquote>\n

I got partway through the list and my problems with the example went away. I wasn’t as diligent as I should have been tracking which step actually fixed it, but was happy enough it worked! <\/p>\n","protected":false},"excerpt":{"rendered":"

A while back, I had some problems with Apple’s Core Data ‘Core Recipes’ example. I couldn’t find anything on Google, so I emailed a friend of a friend at Apple, and ended up getting some VERY helpful troubleshooting tips from … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[24],"_links":{"self":[{"href":"https:\/\/fhmiv.net\/blog\/wp-json\/wp\/v2\/posts\/252"}],"collection":[{"href":"https:\/\/fhmiv.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fhmiv.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fhmiv.net\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/fhmiv.net\/blog\/wp-json\/wp\/v2\/comments?post=252"}],"version-history":[{"count":0,"href":"https:\/\/fhmiv.net\/blog\/wp-json\/wp\/v2\/posts\/252\/revisions"}],"wp:attachment":[{"href":"https:\/\/fhmiv.net\/blog\/wp-json\/wp\/v2\/media?parent=252"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fhmiv.net\/blog\/wp-json\/wp\/v2\/categories?post=252"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fhmiv.net\/blog\/wp-json\/wp\/v2\/tags?post=252"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}