Apparently People works on Android 2.0, but only searches the default group, meaning contacts inside groups will not be accessible via People. Also, the Android 2.0 emulator doesn't support groups at all, so there's no way to even program for 2.0 unless you have a 2.0 device, which is a huge expense.
This release was a mess. It's definitely affecting my productivity greatly by limiting my ability to program for Android 2.0. On Tue, Nov 17, 2009 at 12:33 PM, DonB <[email protected]> wrote: > Did you find a solution? I have the same issue. > > > On Nov 15, 9:29 pm, Ryan Rowland <[email protected]> wrote: > > Sorry, I didn't proof-read, correcting mistakes... > > > > I'm implementing a new "import" feature into an app I have that's already > > been published, designed to show your current list of contacts with a > > check-mark next to them, letting you select which you would like to > import > > into the app. However, I'm looking to serve all platforms: 1.1, 1.5, 1.6, > > 2.0, which doesn't seem possible. It seems that I now have to choose > whether > > I want my app to be available to 2.0 or prior to 2.0, alienating all of > my > > prior customers. > > > > The problem is the People class is deprecated in 2.0, and doesn't work. I > > must use ContactsContract. However, I can't use ContactsContract unless I > > include the 2.0 SDK which requires the user have a 2.0 phone. So it has > to > > be one, or the other. It doesn't seem like there is a way around it. Am I > > missing something? Is there a method that will work across the board, or > am > > I forced to severely dwarf my potential market by choosing which SDK(s) I > > want to support? > > > > -Thanks, > > Ryan Rowland > > > > On Sun, Nov 15, 2009 at 7:27 PM, Ryan Rowland <[email protected] > >wrote: > > > > > I'm implementing a new "import" feature into an app I have that's > already > > > been published, designed to show your current list of contacts with a > > > check-mark next to them, letting you select which you would like to > import > > > into the app. However, I'm looking to serve all platforms: 1.1, 1.5, > 1.6, > > > 2.0, which doesn't seem possible. It seems that I now have to choose > whether > > > I want my app to be available to 2.0 or prior to 2.0, alienating all of > my > > > prior customers. > > > > > The problem is the People class is deprecated in 2.0, and doesn't work. > I > > > must use ContactsContract. However, I can't use ContactsContract unless > I > > > include the 2.0 SDK which requires the user have a 2.0 phone. So it has > to > > > be one, or the other. It doesn't seem like there is a way around it. Am > I > > > missing something? Is there a method that will work across the board, > or am > > > I forced to severely dwarf my potential market by choosing which SDKs I > want > > > to support? > > > > > -Thanks, > > > Ryan Rowland > > -- > You received this message because you are subscribed to the Google > Groups "Android Beginners" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<android-beginners%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-beginners?hl=en -- You received this message because you are subscribed to the Google Groups "Android Beginners" 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-beginners?hl=en
