Comments on: Adding New Development Devices

By: sharon

sharon — Thu, 30 Jul 2009 23:03:53 +0000

In addition to the iTunes copy workaround, there’s also a free app “BetaHelper” which grabs the UDID (+OS etc) and emails it to the destination of your choice. Perfect when you’re feeling too lazy to go to the desktop.

By: Oguzhan Topsakal

Oguzhan Topsakal — Thu, 23 Jul 2009 12:34:16 +0000

Thanks for the information. You saved me a bunch of time. I could make an addition:
In the Xcode organizer, there is a ‘iPhone Development -> Provisioning Profiles’ section. After updating and then adding the updated profile to your device, you will see two profiles in the this section. One of them is old, the other one is the new updated one. If you delete the old one, everything is gonna be all right.

By: iPhone Developer Program Gotchas

iPhone Developer Program Gotchas — Wed, 11 Mar 2009 21:07:50 +0000

[...] 6. Adding provisioning profiles. Forget about dragging them on XCode and manage them manually. Check out my earlier entry about it. [...]

By: Noel

Noel — Mon, 02 Mar 2009 18:14:57 +0000

Thanks, Ramses. I didn’t know you could copy the UDID from iTunes since you can’t highlight it! What a horrible interface, but that’s great to know. Thanks!

By: Ramses

Ramses — Mon, 02 Mar 2009 18:12:19 +0000

Hi Noel,

Here is a little tip for when you are going to ask your beta testers to send their UDIDs. Chances are they won’t have XCode installed on their computer. Luckily, copy-paste also works from within iTunes:
- open “Summary” tab
- click “Serial Number” -> it will change to Identifier
- command-C to copy (you do not have to select the text)
et voilà, the 40 characters-long UDID is now in your clipboard!

Here is another tip to know what provisioning profiles in ~/Library/MobileDevice/Provisioning Profiles correspond to. In XCode Organizer (Command-Control-O), there is a “PROVISIONING PROFILES” section from which you can select each profile and you’ll be able to see its corresponding mangled file name as well as some extra information (such as the number of devices in the profile, the App Identifier, …).

I hope this helps.

Cheers.

By: Andrew Pouliot

Andrew Pouliot — Sat, 28 Feb 2009 20:31:56 +0000

Hey, what you should really be doing is installing provisioning profiles manually into ~/Library/MobileDevice/Provisioning Profiles with Xcode closed, then go back into Xcode and select the new PP at the project level. This smoothes out a lot of issues because it doesn’t screw up the names of your provisioning profiles, and you can actually remember which is which.

You’ll also want to hit delete on the target level setting for code signing identity so it just reflects the project level setting.

Hope that helps!

By: Patrick

Patrick — Sat, 28 Feb 2009 19:17:35 +0000

Thanks for the comments I was having trouble install the provisioning profile on the iPod. Deleting all of them manually while xcode was off. Then starting xcode, install the profile, and run on the iPod worked like a charm. Thanks!

By: hkk

hkk — Sat, 28 Feb 2009 08:31:47 +0000

I think because people don’t understand the differences between installed SDK, target SDK and firmware version. I haven’t seen an Apple document that gives good explanations and guidance on this.

By: Noel

Noel — Sat, 28 Feb 2009 04:08:33 +0000

Actually, I’m targeting 2.2 for Flower Garden. I started using AVAudioPlayer and it’s hard to give up (it’s a 2.2 feature). I’m not too concerned though. There seem to be lots of apps in the top 20 that require 2.2 (even some of them 2.2.1 why????)

By: hkk

hkk — Sat, 28 Feb 2009 03:41:12 +0000

Yes, it is a bit of a pain. I always delete the old profile manually like you describe and also quit XCode before installing the new one. I also completely delete the build/ directory.
As for the firmware version: It makes sense to target firmware 2.0 as far as I know. That way you don’t exclude any potential customers. Of course if you need features introduced later, you need to use a later version. But Apple has barely introduced any new features in its SDK updates so far, so most apps can target 2.0 without any problem.