As has been discussed on this list, the 2.0 Contacts API is a significant overhaul. And that the 1.6 API has been deprecated. Usually this means use of the 1.6 API is discouraged but maintained for at least a little while. I am not that this is the case, however. The app I'm working on was built and tested for 1.6 and is now failing in the contacts code when built for 2.0. Does anyone know how Google intended us to target/support both 1.6 and 2.0 platforms in the same build? It seems we have to query for the api level (or at least, reflect for ContactsContract) and execute api level specific code. Yes/ No?
Thanks. -- 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
