Hi all,
I recently experienced the cyclic - and somewhat random:
"Android.process.acore has stopped unexpectedly"
problem and googling it mostly came up with nothing and in a few cases
"fixed it by wiping the phone".
I found that unsatisfactory, so I decided to dig deeper. To me it was
pretty clear that this was sync related - turning off Contacts sync
stopped it from happening. Turning it back on will trigger the problem
within a few seconds.
So it would seem that something in my G1 Contact database will not
transfer to Gmail's Contact database. Sadly I could not find any useful
trace, but at least I knew roughly when it had happened.
By comparing what I could see in the database and what actually was
visible in the Contact Editor I tracked it down to that I had some
Contact Postal Addresses that had a TYPE with a value > 3.
In the editor these will still show up as "HOME" ("Other" would have
been more appropriate IMHO). If I fiddle this to some other value and
save the contact again the problem disappears.
In my opinion it would make sense for the acore sync process to handle
incorrect values by replacing them with HOME/OTHER instead of crashing.
I have not dug into the source, but I would think it would be a trivial
fix. I suspect there might be several similar cases where a default
fallback would make more sense than to crash the sync.
In retrospect I also know how this happened to me: I optimistically used
the Phone label to produce a Postal Address label - it never occured to
me that they could be different.
Best / Jonas
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
