> That only tells you about stuff you are doing. Which can't be kept in sync > with what is actually in the database, and doesn't prevent you from > colliding with anything already in there.
Duplicate contacts aren't that much of a nuisance, imho. They're easy to fix and prevent. Specially if you consider the other option is adding another permission, going against Google's own best practices that we should use the least permissions possible. > What is it that you are actually trying to do here? Consider, por instance, a database of contacts of sports clubs. Put them in a map and let the user choose to add a contact for the local club by adding a button. The app "stores" the addition and warns the user if he tries again to add the same contact. This is NOT "blindly stuffing" a contact, as you said, it is a normal response to a user action. If writing a contact is and will be impossible without the READ_CONTACT Google should at least assume READ_CONTACT after adding WRITE_CONTACT in the manifest.xml. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
