LO87837: ANDROID/IOS VERSE DEVICES SYNCING ONLY 16 BYTES OF CALENDAR DATA INSTEAD OF AT LEAST 100,000 BYTES PER MESSAGE
Direct links to fixes
Closed as program error.
Android or iOS Verse clients were syncing but taking a long time or not completing because the server was only sending 16 bytes of real data to the client per message. The sync was still going, but took hundreds of SyncML messages for a 1MB calendar event instead of about 10. The calendar event had enough multiple byte UTF-8 characters to hit an error in a size calculation that caused it to default to the 16 bytes of data along with <MoreData/> to carry the sync data over into the next message of the overall SyncML sync. This error depends on the characters and the size needed for the HTTP message boundaries, so it is not a common scenario.
Workarounds include removing the calendar event, modifying the calendar event's description, and removing some exceptions to the event.
Some Calendar events would take a while to sync. The scenario is not common and would be triggered by specific double byte character combinations in the description.
The IBM Traveler server has been updated to handle this scenario correctly.
This fix will be included in IBM Traveler 18.104.22.168 and all future releases. For the latest available maintenance release see this technote: http://www.ibm.com/support/docview.wss?uid=swg24019529
Reported component name
LOTUS NOTES TRA
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
LOTUS NOTES TRA
Fixed component ID
Applicable component levels