Comments on: iPhone Developer Program Gotchas (or what I learned the hard way)

By: links for 2009-04-16 « Blarney Fellow

links for 2009-04-16 « Blarney Fellow — Thu, 16 Apr 2009 18:37:07 +0000

[...] iPhone Developer Program Gotchas (or what I learned the hard way) (tags: iphone viapss) [...]

By: linkfeedr » Blog Archive » Links for 2009-04-14 [del.icio.us] - RSS Indexer (beta)

Wed, 15 Apr 2009 07:02:02 +0000

[...] was found on Tenerife Skunkworks. Click here to visit the full article on the original website. iPhone Developer Program Gotchas (or what I learned the hard way) Remixing OpenGL and UIKit Using Multiple OpenGL Views And UIKit iPhone Software Development: OpenGL [...]

By: Billy Zelsnack

Billy Zelsnack — Fri, 13 Mar 2009 22:29:52 +0000

I don’t zip up my apps to send to people anymore. It’s easier to drop your app into itunes yourself and grab the resultant .ipa file from the the ~/Music/iTunes/”Mobile Applications” directory. That file will work for both windows and osx users. It also seems to confuse itunes less when a tester drops it in.

I also have never encountered #7. I’ve heard people say the same thing about submitting for the app store, but I’ve not encountered a problem there either.

By: Pete

Pete — Thu, 12 Mar 2009 14:51:30 +0000

I want to put apps on App Store but I wonder about privacy and registering as an individual vs. registering as a business. I’d rather not share my home address and home phone number with everyone who visits app store, even those who buy my app. Is your personal contact information kept private? Or if you register as a business using a mailbox address does Apple require mountains of documents to prove that is your business address? Do you have to settle these matters before you can even test your app?

By: Hendrik

Hendrik — Thu, 12 Mar 2009 08:04:21 +0000

Vic: Once your app gets accepted, you go into iTunes Connect, choose “Edit Application”, go to the Pricing page and change the date there to the current date. You do the same for every update that you publish too.

I am quite sure Ramses is correct. The target settings should override the Project settings.

An extra tip: I made it a habit to always go nuclear and delete the complete build/ directory in the Finder before building for the App Store. I have had inexplicable upload failures several times before and since I started doing this every upload has worked fine.

By: Noel

Noel — Wed, 11 Mar 2009 22:48:09 +0000

Ramses, Really?? It’s certainly disconcerting that those two settings don’t match up. I could have sworn that if either one of them was off, the build wouldn’t be recognized by the device. But maybe the target one was the one that was off. I’ll double check.

By: Ramses

Ramses — Wed, 11 Mar 2009 22:38:57 +0000

“7. Set correct provisioning profile everywhere.”: setting the provisioning profile for the target in the current configuration should be enough (it works for all our projects) as it overrides the more general project settings. Think of it as just an extra layer to override defaults defined at project level.

By: Vic

Vic — Wed, 11 Mar 2009 22:22:05 +0000

When submitting an App for approval, you have to enter the “Availability Date” in iTunes Connect. The default is the day you are submitting the App. If you leave it as the default and the App is approved 5 days later, the Availability Date doesn’t get automatically adjusted. It stays at the original date. The problem with that is, it doesn’t show up in front of the App Store’s new releases list which is sorted by Release Date.

I want this date to be set to the day the app gets approved. But without knowing how long it takes for the approval process, it is hard to figure out what date to set. Any suggestions?

By: Ari Braginsky

Ari Braginsky — Wed, 11 Mar 2009 21:25:52 +0000

Another one I found recently when I went to submit my Librarian application to the App Store was that the bundle identifier in the Info.plist cannot have a wildcard or any other character that would be illegal for a domain name, even if your provisioning profile uses a wildcard.

Since I had originally created a wildcard provisioning profile, I was using the wildcard for local development:

com.guidanceisinternal.*

I was able to build to both the simulator and the device with this.

After using the keyword for the current app name in place of the wildcard the App Store accepted my submission:

com.guidanceisinternal.${PRODUCT_NAME:identifier}

Hope this helps someone!

By: Tommy

Tommy — Wed, 11 Mar 2009 21:21:23 +0000

Regarding number 5, I use this command to zip my apps for the app store:

ditto -c -k -X –keepParent AppName.app/ AppName.app.zip

I cant tell you exactly why that works, but I know it does! Ditto is apparently some OSX super command that plays nice with resource forks, and copies or zips files.

I feel more comfortable when my production builds come from the build system, rather then by manual process.