| Description | I created a test account in SOGo (current Debian jessie installation, current 3.0.1 SOGo packages) and configured it as "Exchange" account on the Android client.
java.lang.ArrayIndexOutOfBoundsException: length=3; index=3
at com.android.exchange.utility.CalendarUtilities.getLong(CalendarUtilities.java:196)
at com.android.exchange.utility.CalendarUtilities.tziStringToTimeZoneImpl(CalendarUtilities.java:811)
at com.android.exchange.utility.CalendarUtilities.tziStringToTimeZone(CalendarUtilities.java:766)
at com.android.exchange.utility.CalendarUtilities.tziStringToTimeZone(CalendarUtilities.java:782)
at com.android.exchange.adapter.CalendarSyncParser.addEvent(CalendarSyncParser.java:442)
at com.android.exchange.adapter.CalendarSyncParser.addParser(CalendarSyncParser.java:1069)
at com.android.exchange.adapter.CalendarSyncParser.commandsParser(CalendarSyncParser.java:1139)
at com.android.exchange.adapter.AbstractSyncParser.parse(AbstractSyncParser.java:190)
at com.android.exchange.eas.EasSyncBase.handleResponse(EasSyncBase.java:109)
at com.android.exchange.eas.EasOperation.performOperationInternal(EasOperation.java:327)
at com.android.exchange.eas.EasOperation.performOperation(EasOperation.java:266)
at com.android.exchange.eas.EasSyncBase.performOperation(EasSyncBase.java:125)
at com.android.exchange.eas.EasFullSyncOperation.syncMailbox(EasFullSyncOperation.java:263)
at com.android.exchange.eas.EasFullSyncOperation.performOperation(EasFullSyncOperation.java:196)
at com.android.exchange.service.EasService.doOperation(EasService.java:419)
at com.android.exchange.service.EasService$1.sync(EasService.java:134)
at com.android.exchange.service.CalendarSyncAdapterService$SyncAdapterImpl.onPerformSync(CalendarSyncAdapterService.java:131)
at android.content.AbstractThreadedSyncAdapter$SyncThread.run(AbstractThreadedSyncAdapter.java:259) |
|---|
| Steps To Reproduce | Create an empty SOGo test account.
Create at least one calendar entry with SOGo webinterface.
Synchronise Account (either just wait, update E-Mails or cycle the "Sync Calendar" option in the Exchange account setting).
-> "Unfortunately, Exchange Services has stopped." occurs. Report shows above backtrace. |
|---|
| Additional Information | I'm located in austria, timezone is "central european time".
User Language Setting in SOGo is German.
Android device language is set to English.
If the calendar event is created on the Android device it doesn't crash at first. I assume because the event doesn't have to get synchronised. If you remove the account from the Android device or reset the device using sogo-tool manage-eas then the crash happens with the Android created calender event too.
I sniffed the data traffic using "tcpdump -i lo -w TestEvents.pcap -s 0 -A tcp and port 20000".
There are two events: TestEvent1 and TestEvent2. TestEvent1 was created on the Android device, TestEvent2 in the SOGo webinterface.
I tried to only sniff data from this single client during the crash but I can't guarantee there was absolutely no different traffic captured too. |
|---|
