How are you validating that your own contacts database is still in sync with the device contacts data? As you mentioned: the ID can change over time. According to the API docs it can even change on synchronization and / or account aggregation not just when the user switches phones.
You should take a look at the contact LOOKUP_KEY<http://developer.android.com/reference/android/provider/ContactsContract.ContactsColumns.html#LOOKUP_KEY>. It is a string that helps finding a contact even when the ID did change. This link here<http://developer.android.com/guide/topics/providers/contacts-provider.html#ContactBasics>also contains a bit of information about the lookup key. On Thursday, January 31, 2013 3:43:30 AM UTC-6, Tom wrote: > > Hi guys, > > I write an app which should use an own account for contacts. > I found a lot of examples in the internet but not that what I want. > And the SampleSyncAdapter from the samples doesn't help me so much. > > What I want is a something like > > AccountManager _accountMgr = AccountManager.get(context); > Account [] accounts = _accountMgr.getAccounts(); > final Account account = new Account(accounts[0].name, "com.myapplication"); > mAccountManager.addAccountExplicitly(account, null, null); > > What I don't want is a new account where I have to input a username and a > password. > > The issue is, that my app reads the contacts and in the moment I'm using a > sqllite database where I store > the contactid and further information to this ID which my app needs and which > I can't store in the normal contacts. > Normally no problem. But what happened if someone needs a new smartphone. > Contacts you can export and import in your new phone. > But during the import the contactid could change. Then my app can't link the > contactid which I stored in my SQLLite-database to the > right contact in the new smartphone. > My idea was, to create an new account for my app (like "WhatsApp" is doing > that) and storing there my additonal contactinformation. > This account I can export and import it to a new smartphone. > > That's right, or? But for that I don't need an AuthenticatorActivity with > username and password. > I only need a new account. > > How can I solve that. > Thanks for any help > > BR > Tom > > > > > -- -- 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 --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
