Closing as "Not a Bug", though I did make some optimizations and added 
some more unit tests based while trying to debug the report - so not a 
total wash ;)

It seems that you are right. After i cleaned the device completely and 
also my database now the exceptions are transmitted. I already did a 
cleanup of the device but it did not work.

So for me it looks like we can close this bug, thanks for looking after it.

With regards

Jonathan Westerholt

Also, since both I, and others, have exceptions working on multiple 
android devices - this leads me to believe the missing exceptions are 
due to something else.

Unless I'm totally missing something here, it's only ignoring the tag 
(BodyTruncated) that it doesn't recognize. It would still continue to 
parse the remaining properties of the exception.  Where do you see 
that the exception itself is ignored?

Regardless, thanks for pointing out the code for this, there is some 
really helpful information there.

I had a look at

http://grepcode.com/file/repository.grepcode.com/java/ext/com.google.android/android-apps/2.3.5_r1/com/android/exchange/adapter/CalendarSyncAdapter.java

In line 778 there is the implementation of the exception parsing (just 
add #778 to the above link).

The complete parsing starts at addEvent() in line 384.

with regards

Jonathan Westerholt

Changes have been made in Git for this ticket:

Bug: 10856  Exceptions only support a subset of Appointment's properties.

  1 files changed, 33 insertions(+), 22 deletions(-)
http://git.horde.org/horde-git/-/commit/d7844393b34c26d3b80402d1815b87411a0ee26d

Do you see a list of supported properties in the adapter source code 
that you could share, or perhaps a link?

It's my understanding that exceptions support the same properties that 
appointments do (except those that make absolutely no sense, like 
"EXCEPTION"), since that's what they essentially are.

That being said, this wouldn't be the first time the documentation is 
unclear, and we never use the bodytruncated property on outgoing 
messages anyway, so should be OK to remove it from Exception messages.

When syncing my Desire HD (Android 2.3.5) exceptions are not synced to 
the device.

When looking into the log i see that the "BodyTruncated" Tag is sent 
with the exception (see attached log, it is only one add entry).

After digging into the source code of the android sync adapter it 
looks like android is throwing away the event if an unknown tag is sent.