Rachel Blackman wrote: > I am reasonably certain that if you compile the app for 1.6 but run > on 2.0, the contacts code will work. The caveat here is that you > will only get the raw contacts from the master account, rather than > the combined contacts from all active accounts; the older API just > doesn't have the functionality needed to handle combined accounts.
Not from what I can tell, or perhaps I'm just misusing terms. The rest of this week is my ContactsContract Comprehension Project (da, CCCP, komrade!), so I'm playing with this stuff right now. If you try to do an Intent.ACTION_PICK on Contacts.People.CONTENT_URI, on a 2.0 emulator with contacts manually added via the Contacts application, with an app targeting API 4 or 5, the picker fails to find any contacts. If you try it on a DROID, you get manually-added contacts plus others culled from heaven knows where. If you use ContactsContract.Contacts.CONTENT_URI instead, it works fine on the 2.0 emulator and the DROID. Of course, that doesn't work on Android 1.6 and below. But, my investigation continues -- it may just be an ACTION_PICK hiccup. Or, I may be misinterpreting something. BTW, many many thanks for your work in marshaling information about the contacts APIs! -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android Consulting/App Development: http://commonsware.com/consulting -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
