Il problema è legato ad un cambiamento di Apple per l'identificato del dispositvo EAS Sync ID utilizzato per identificare il device ID ed il problema dovrebbe avvenire in fase di nuova registrazione del device all'uso di traveler e non per i device già configurati.
Una spiegazione dettagliata del problema la si può trovare su questo Blogger
Ecco la lista dei Bug risolti con questo rilascio
APAR # | Component | Abstract |
LO81050 | Server | Too many instances of a calendar event may prevent Notes Client from displaying the event. |
LO81078 | Server | Reply to meeting notice may get delivery failure if lookup fails for canonical name. |
LO81115 | Android | Rotating device during corporate lookup may result in two progress bars. |
LO81121 | Android | Compose mail on Android may display as double spaced for the recipient. |
LO81174 | Android | Corporate lookup from Contacts app not showing all fields available. |
LO81208 | Android | Auto sync may be disabled after upgrade of Android client. |
LO81358 | Android | Wipe command for Android shows as pending even though it was executed on device. |
LO81446 | Server | Newly registered user may fail to sync all folders with Apple device. |
LO81493 | Server | Very large plain text e-mail could impact server performance. |
LO81514 | Server | Some attachments may not download to Mobile device. |
LO81546 | Server | Approval pending devices may not show up in the device security view of web administrator. |
LO81574 | Server | Drifting OS Clock could result in one or more Traveler HA servers being marked as offline. |
LO81611 | Server | Device may resync data if sync requests received out of order. |
LO81640 | Android | Sound notification on Android for new mail may play more then necessary. |
LO81602 | Android | Device approval for Android device may not be sent in the device language. |
LO81628 | Server | Defrag of derby database should rebuild constraint indexes. |
LO81659 | Server | Attachment may not download when name includes iso-2002-jp encoded special characters. |
LO81719 | Server | iOS8: Support Out of Office departure and returning dates for ActiveSync devices. |
LO81732 | Server | Cleanup orphan user and device entries from web administration views. |
LO81743 | Server | Attachment may not download when has Ampersand in the name. |
LO81748 | Server | Apple device may get stuck in a Calendar sync loop. |
LO81757 | Server | User listener registration may fail if Traveler database is not reachable. |
LO81815 | Server | Send mail from older Windows Phone device may have corrupt UTF-8 characters. |
LO81842 | Server | iOS8: Support registering new Traveler Companion and ToDo applications on Apple iOS 8.x devices. |
LO81898 | Server | Update the Apple Push Network (APNs) certificates. |
LO81908 | Server | Device may stop receiving updates if MIME parse error encountered. |
LO81909 | Server | iOS8: Accepting an unprocessed reschedule on Apple device may result in two copies of event on the device. |
LO81910 | Server | iOS8: Delete instance of a repeating event on Apple device may send recipients multiple update notices. |
LO81913 | Server | iOS8: Traveler Companion and ToDo applications may not be able to utilize full capabilities on Apple iOS 8.x devices. |
LO81914 | Server | Send mail cache could miss a duplicate mail send instance in an HA environment. |
LO81916 | Server | Call to getLocalHost could impact sync performance. |
LO81919 | Server | Send e-mail to self may not sync to Inbox on mobile device. |
Da questo link è possibile visionare/scaricare le diverse fix pack: http://www-01.ibm.com/support/docview.wss?uid=swg24019529
3 Commenti:
sto usando la 853-up2-if7 e con android non ci sono problemi di allegati, consiglio l'uso dell'app presente sul play market (ora alla versione 9.0.1.3)..
UPDATE: il supporto IBM ha una versione aggiornata dell'apk per Android che pare risolvere il problema.
non mi pare sia pubblica, va richiesta al supporto.
ATTENZIONE: la IF7 di Traveler comporta un problema con gli allegati su dispositivi Android. In alcuni casi non si riescono a scaricare con annesso messaggio di errore.
Problema confermato da IBM. Attualmente consigliano di fare un downgrade alla IF5, perchè il problema sembra ci sia fin dalla IF6..
Da capire cosa succede a chi ha già aggiornato gli iphone a iOS8, la cui compatibilità c'è dalla IF7..