Archive for June, 2009
Well That Didn't Take Long
Jun 29th
As you can see we are now flying under a new banner: Core Fruition! In less than two hours from my last post I had the answer to my naming quandary from Paul Goracke, and I can’t thank him enough.
When I saw Paul’s suggestion my first thought was, “That’s an awesome name!”. My second thought was, “That sounds really close to another popular Cocoa site…” Not wanting to step on any toes, I decided to throw the name into some focus testing, asking a bunch of high ranking folks for their gut reaction. Here are the results:
Mickey Roberson: “That’s not bad“
Bill Dudney: “Frution is too ‘hard to read’, but not gut reaction is I like it … cool name“
Danny Greg: “rip off of core intuition, other then that – nice“
Jeff LaMarche: “I like it.“
Dave Verwer: “I like Core Fruition“
Brent Watson: “I like it“
Marcus Zarra: “I like it. Makes me think of learning cocoa“
As you can see, most folks liked it with only Danny giving me the reaction I was afraid of, which wasn’t enough to keep me from pulling the trigger. I’d like to thank everyone for submitting names and cool ideas, and especially Paul for hooking me up with a winner. Now, if some intrepid graphic designer would like to hook me up with a sweet logo…
I am Not a Name Thief
Jun 29th
Not intentionally, anyway. First a little back story: When I was trying to decide on a name for this blog I would come up with what I thought was a great name and then plug it into Google to make sure that it wasn’t already taken. Most of the time I would find a blog that already had the same name and move on to a new round of brainstorming. When I arrived at the name “Cocoa Nut” I thought for sure it would be taken. I did a quick search but found no hits for that name having anything to do with programming in the first few pages of search results. I thought, much to my amazement, that I had struck blog naming gold, I couldn’t believe my luck!
Apparently my brain decided to ignore the third entry on the first page of Google results
Fast forward to last week. I was looking up some show notes on the Mac Developer Network when I noticed the blog roll on the side of the page. Curious if my blog was listed there (I had submitted it to Scotty a while back) I took a quick glance through the list and saw Cocoa Nut sandwiched between Call Me Fishmeal and Cocoa Samurai. I clicked through expecting to be greeted with my blog’s homepage but was instead taken to a different Cocoa Nut.
The original Cocoa Nut
Astounded, I quickly checked his archives, sure that he had shown up on the scene after me and had not been thorough enough in his search for naming collisions. 2006. His first post was from 2006. My first post was in 2008. I was sunk.
So back to the title of this post: I am not a name thief. I am currently searching for a new moniker for this blog. Yes, I could make the argument that in a fully qualified world his Cocoa Nut and my Cocoa Nut are in completely different namespaces and that they don’t collide, but that’s BS and everyone would know it.
Therefore, if you’d like to suggest a name, please feel free. Otherwise, I will be thinking and Googling until I come up with something that no one else has thought of yet.
Bypassing the Trouble Caused by Updating an iPhone App Provisioning Profile
Jun 19th
[UPDATE] After many discussions on Twitter and many recommendations by different folks, I think that we have determined that the method outlined below is not necessary. Mike Taylor has hit upon what appears to be a foolproof method for getting around the trouble caused by updating an iPhone app provisioning profile, and best of all, he did it in 140 characters:
@kalperin @MrRooni Delete old profile from Organizer. Download new profile ‘n drag to organizer. Restart Xcode. Choose new profile in target
Many thanks to Mike for helping me out here, I owe you a beer at WWDC10. For those of you interested in the more masochistic way to get around the issues, feel free to continue reading:
A note before I begin: Everything below was done with the final build of the iPhone OS 3.0 SDK and I was building an app using the 2.2.1 frameworks.
I recently acquired a new iPod touch to use a development device. One of the first things that I wanted to do was get my existing project up and running on the device so I headed over to the iPhone Development Program Portal to update my provisioning profile.
After adding the new device to my app’s provisioning profile I downloaded the updated profile and installed it into Xcode and onto the device via the Organizer. So far so good, everything up until this point worked exactly as I expected it to.
Switching back to my project I changed my build settings to be a Release build under 2.2.1 on the device. The app built fine, but I got an error when it tried to install the app onto the device, something error akin to “This device doesn’t contain the provisioning profile with which this app was built”. Thinking that maybe Xcode just hadn’t seen the new profile yet I cleaned all targets in my project, restarted Xcode and tried again. No dice, same error as before.
I then proceeded to delete all versions of the profile from the organizer and re-installed the new one. My assumption was that once Xcode saw that the old profile didn’t exists anymore it would switch over and use the new one. I cleaned all targets and built again. This time I was treated to a different error: ”Code Sign error: Provisioning profile ‘3E6AA725-6534-46F8-B9CE-D19AC9FD854B’ can’t be found”
After a bit of Googling I discovered that Xcode stores the ID of the provisioning profile in its project.pbxproj file. This discovery led me to the fix:
- Close your Xcode project
- Navigate to your project folder in the Finder
- Right click on your .xcodeproj file and ‘Show Package Contents’
- Drag the project.pbxproj file to Xcode (or any plain text editor)
- Perform a search for the term ‘provision’ to find the PROVISIONING_PROFILE entry.
- Copy the existing profile ID and paste it into the find field of a find and a replace dialog.
- Open up the Organizer window (Window menu > Organizer) and navigate to your new profile under IPHONE DEVELOPMENT > Provisioning Profiles
- Click on your provisioning profile and copy its Profile Identifier
- Paste the string into the replace field in your open find and replace dialog.
- Replace all instances of the identifier, save the file, close it, and reopen your Xcode project.
- That should do it, build and go to run your app on your new device.
Now there is a great possibility that I am going WAY overboard here and missing a very obvious way to accomplish the same solution. If that’s the case please let me know in the comments.
