How USB Charging in iProducts Works
This may seem tirade-ish, and if so I'm sorry. This was spurred by the story posted here at TUAW. Basically, there's a little USB pass through dongle that you can buy to eliminate your iPad "not charging" woes. TUAW kind of misses the boat on bothering to explain or understand it, so here's how it works, in comment-on-the-article form (so read the article first):
Backgrounder vs. Build and Run
This is what happens when you Build and Go with Backgrounder running.
Here's a quick note on how Backgrounder, from the wonderful http://twitter.com/ashikase interacts with Xcode's Build and Run functionality.
Developing for a Jailbroken iPhone A to Z (iOS 4.0.1)
Jailbreak Development for iOS4!
Vital Stats:
iOS 4.0.1
Xcode 3.2.3
Mac OSX 10.6.4 Snow Leopard
iPhones 3G, 3GS, 4 (I finally have the whole lineup!)
PROBLEM: I still can't get iPhone 4 working. If you have one, please try it and help me out! UPDATE: Found the cause of the problem to be certain status bar libraries installed alongside other apps. I'm not sure why they cause the problem, but see full notes at the bottom of the post.
The Goal: As usual, we want to be able to click "build and go" in Xcode and get the app we're working on to load to the phone and start up. Also, we want to be able to debug from within Xcode itself. After all, Xcode is cool, and terminal+makefiles+gcc+gdb is lame.
Developing for a Jailbroken iPhone A to Z (iPhone 3.1.2)
Debugging on device. Freaking finally.
UPDATE: There's a new method for iOS4 but they're pretty similar anyway.
So it's been a while, but now that I'm on break again and have some time, I'm doing a bit of iPhone development again. That means I'm going to need to debug on-device (or at least load my app to it to have fun in the real world with my handiwork). This time, the procedure's a little different though.
Vital stats:
iPhone OS 3.1.2
Xcode version 3.2.1, 64 bit
Mac OSX 10.6.2 Snow Leopard
Let's do it.
UPDATE: Corrected a problem with the run script build phase: corrected the directory names for the new version and copied the new phase that doesn't include "resource_rules.plist."
UPDATE 2: Somehow I forgot the add an identity step. It's now #1 below. Sorry guys. Also, while this whole thing should apply to iPhoneOS 4, I'm going to officially text it/repost with 4.01 soon.
Simulator Seem to be Stuck on 2.2.1?
ARG! It's stuck!
So maybe this is the dumbest, easiest thing in the world and I'm the only one who didn't know, but when I upgraded to the iPhone OS 3.0 SDK, I couldn't for the life of me get the simulator to launch in ACTUAL OS 3.0 mode. You can change the version on the fly with the Hardware>Version menu, but every time I reran my app from Xcode, it'd revert back to 2.2.1. This finally became a problem when I needed to test an app with features unique to 3.0. Luckily, the fix isn't all that hard.
Gizmodo is dumb – ATT Visual Voicemail Fix
#gizmodofail
If you have an iPhone and have not had visual voicemail for weeks, it's actually your fault, even if you didn't know it. When you downloaded that little file to enable tethering, the maker actually messed up. The file from gizmodo had the Visual Voicemail APN set to wap.cingular, which is incorrect. It should be acds.voicemail. The fix is easy: go to settings>general>network>cellular data network and edit the Visual Voicemail APN as above to read acds.voicemail. Restart your phone and everything will work again.
NOTE: The fix above only works if you're jailbroken and you have the package "APN Editing" installed. I think you can also expose this menu with unlockit.co.nz (but be careful, the normal profile they use for ATT US carrier, mms/tethering enabled has the wrong APN for vvm, reset it as above). I'm trying to modify the carrier profile from gizmodo to correct the issue in the first place.
Using the Open Tool Chain in Xcode (for both OS 2.2 and 3.0)
OTC =/= Over the counter, but it WILL cure what ails ya.
The iPhone OS SDK from Apple is wonderful, and being able to develop and debug on-device even without paying the entry tax is even more wonderful. To really take Jailbreak development to the next level, though - to develop Apps that don't play nicely in Apple's SDK playground - you are going to need the open tool chain. Here's how to rock Xcode OTC style.
Developing for a jailbroken iPhone, A to Z (iPhone 3.0)
Rockin 3.0
UPDATE: NEWGUIDE NEWGUIDE NEWGUIDE!
Vital iPhone stats for this post:
iPhone version: 3G (should work with 2G and 3GS)
iPhone OS version: 3.0 (rock the hizzouse!)
Jailbreak status: Jailbroken using Pwnage Tool.
The Goal: Get live on-device XCode debugging without being a paying ADC member. This time OS 3.0 style.
Hold on tight, 3.0 sdk info coming soon
UPDATE 7/11/09: Procedure working great: post here.
Everyone's getting antsy about on-device debugging with SDK 3.0, which as most of us know broke our preferred method. It looks like the only answer may be to use an outdated version of the SDK, but I'm going to look into it asap. My plan was to use an external drive to install a throw-away virgin copy of OSX. That way, I can experiment and play, and just trash things that don't work so that I know EXACTLY how to install properly. Incidentally, I also need to use this setup for a few similar things at work. The problem is that my MBP's DVD burner is a piece of crud. I say that conclusively because everyone else with a Macbook Pro has the same problems after some time. At this point, it still READS DVDs (mostly) but it can't burn to save its life. My OS disks got horribly marred by someone I loaned them to, and while I had backup images on an external drive, they're clearly not helpful if I can't burn disks 
. Today though, I'll have access to fresh, OEM disks, so I'll get my install going, image it with SuperDuper or Disk Utility, and that should be the ticket. I'll keep you updated, but I expect that I might be able to start working on this after work tonight or tomorrow sometime. In the mean time, the best resource on this problem (and the one that I plan to use to get some procedures going) is http://iphonesdkdev.blogspot.com/.
The Dread Pirate Errorbinson!
Error Starting Executable: No provisioned iPhone OS device is connected.
Ok, lame title, I admit it. That doesn't change the annoyingness of the error though. Here's the story: I sit down last night to watch the Oscars and get my feet wet developing for the first time in maybe a month or two. I go to debug an app on the device, you know, to see if I've still got it, and lo and behold a big hairy error pops up: