Comments on: Cocoa Touch Tutorial: Extract Address Book Address Values on iPhone OS

By: Phoney

Phoney — Tue, 17 Aug 2010 19:35:41 +0000

Yeah, I thought as much. Ho-Hum…

By: Jeff Kelley

Jeff Kelley — Tue, 17 Aug 2010 01:44:14 +0000

Phoney,

I don’t think that the UI is designed to be subclassed; you’d have to create something from scratch.

By: Phoney

Phoney — Mon, 16 Aug 2010 18:54:53 +0000

Hey Jeff,

Is it possible to change anything in the AddressBookUI?
I am looking to capture elements from the standard UI along with some custom fields and I want to extend the UI to achieve this.
Do you know if this is possible or will I need to create my own from scratch?

/Phoney

By: Jeff Kelley

Jeff Kelley — Thu, 12 Aug 2010 02:18:42 +0000

You’re welcome!

By: MadProfit

MadProfit — Wed, 11 Aug 2010 16:23:25 +0000

I want to really thank you for this blog. I have spent 3 days researching as a newbie how to do something like this without writing a lot of code like some of the books suggest (view controllers, arrays, etc) I adopted your code to essentially pull the email address and in the same method get the phone if it isn’t null.

Thanks a lot from the real newbie.

By: ade

ade — Thu, 29 Jul 2010 23:41:09 +0000

oh ok

By: Jeff Kelley

Jeff Kelley — Thu, 29 Jul 2010 19:25:17 +0000

Yes. Since you can’t use the second method, you have to go into the ABRecord yourself and dig out the address.

By: ade

ade — Thu, 29 Jul 2010 19:22:34 +0000

Yea Jeff, that was the method i originally tried and this is probably a dumb question but when i set that method to NO, the address doesn’t show up because it is set in the

-peoplePickerNavigationController:shouldContinueAfterSelectingPerson:property:identifier:

and i cant set it in the first one because the dictionary and array aren’t declared til this method:

-peoplePickerNavigationController:shouldContinueAfterSelectingPerson:property:identifier:

is it possible to just have one method and set all the labels in there.

By: Jeff Kelley

Jeff Kelley — Thu, 29 Jul 2010 18:46:31 +0000

Different method. There are two:-peoplePickerNavigationController:shouldContinueAfterSelectingPerson: and -peoplePickerNavigationController:shouldContinueAfterSelectingPerson:property:identifier:. The first gets called before the second. If you return YES, then the people picker displays individual attributes on another screen (this is where you select the e-mail address, address, etc.) and calls the second method when you select one.

By: ade

ade — Thu, 29 Jul 2010 18:43:56 +0000

i thought that should have been the case as well, but doesnt work for me again, so i must be doing something worng, in my method :
peoplePickerNavigationController:(ABPeoplePickerNavigationController *)peoplePicker
shouldContinueAfterSelectingPerson:(ABRecordRef)person
property:(ABPropertyID)property
identifier:(ABMultiValueIdentifier)identifier {

i return NO, but i am still getting to the address select screen