The following issues have been identified when running the Apple built-in apps for mail and calendar with a Traveler Server:
Duplicate Sent folder entries
Description: As of iOS/iPadOS 13.0, Apple devices add an entry to the Sent folder for any emails sent from the Mail app. When the Sent folder is synced, the server entry is added and the device does not remove the original, resulting in a duplicate. HCL development has opened an Apple bug for this issue (FB7337231).
Workaround: No workaround is available
Accepting a meeting invitation from the iOS device does not send the response to the server
If ghosting is disabled on the Traveler server, responding to a calendar notice from an iOS 13 device does not send the response. The meeting accept is reflected on the app but not in the user’s notes calendar. iOS 13.0 and 13.1 do not send MeetingResponse requests to the Traveler server unless the event is ghosted to the calendar. HCL Development has opened an Apple bug for this issue (FB7328175).
Workaround: Ghosting is enabled at the Traveler server by default. Check the Traveler server notes.ini parameters for NTS_CALENDAR_GHOSTING_SYNCML and NTS_IOS_CALENDAR_INITIAL_GHOST. If found, make sure that they are set to true.
When user click the “Manage the Notes ID” from Traveler home page, there is an error saying: “404 – File or directory not found. The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.”
It is possible that the server administrator changed the URL of the external server when using large “T” in the word “traveler”.
The “External Server URL” configuration of the Notes Traveler tab in the server documents is case sensitive.
Change therefore: https://server URL/Traveler to https://server URL/traveler Restart traveler server
Traveler 10.0.1 FP2 installation package is available on Flexnet. HCL Traveler Documentation – LINK
What’s new in 10.0.1.2?
Updated APNS p12 certificates to replace the files shipped with IBM Traveler 10.0.0 (expire on October 14, 2019). These new certificates expire on June 07, 2020.
Knowledge Base – Customer Support
If a Mail-In Database name has a slash in it, the name returned from the lookup includes CN=, OU=, O=, etc.. Trim these identifiers before returning the lookup result to the client for a more human friendly display.
If a Group name has a slash in it, the name returned from the lookup includes CN=, OU=, O=, etc.. Trim these identifiers before returning the lookup result to the client for a more human friendly display.
Update device security record modification time when device approval action is executed so that the security record is returned by API searches for recently changed security records
Unable to open email attachments in Apple mail client or Verse mobile client for certain type of attachments (example, xlsx file types)
Timing gap between stale connection cleanup and connection registration can cause “Traveler did not respond” errors in the console. The gap is small such that this error is rare, so most “Traveler did not respond” errors are caused by some other reason.
Traveler hang due to MISC threads all being orphaned when S/MIME is enabled for large non-S/MIME messages.
Red status due to User null on thread Alarm-XXXX has been running for XX minutes
EMails restored from archive via iNotes do not sync to device
Improve banned document handling for calendar events
Improve mail streaming performance when MIME-version header missing
Add configuration option, NTS_CALENDAR_INITIAL_GHOST_NOTES_ICS, to prevent ghosting and avoid replication issues for notices created by opening .ics email attachments.
Windows 10.x installer doesn’t remove uninstall entry for 9.x or earlier
Attachments are stripped from plain text mails sent from IMSMO clients
Content Adapter Exception processing Event with Body of type=Text
A draft mail created on Verse iOS defaults to $KeepPrivate=1 when synchronized with the user’s mail file
Allow login name checks to be case insensitive so that user renames that only change the case of some letters also work properly.
Prevent objects over MaxObjSize from syncing on every subsequent sync until deleted, moved to a non-syncing folder or filtered out
tell traveler version reports “running on a VM” when running on real hardware
Improve error handling when schema level is unknown
Performance: avoid reading attachments multiple times during MIME message processing
DB Schema change: Increase the width of the Traveler database’s Exchange ActiveSync version column used to store the protocol version when the device is not security compliant
Update APNS p12 files that expire in October 2019
Pushstatus APIs added in V10.0 are now reported in the output from api/traveler
Although already mentioned, I add this important information to my website. Starting with HCL Verse 10.0.7 for iOS (when it is available), the application is now transferred to an HCL Technologies Apple account and is signed by an HCL-owned certificate.
Expect the following changes:
The Verse application is being rebranded to HCL Verse. Not all references to IBM have been removed in this release.
The Verse application will no longer be able to access any data that the previous IBM signed versions had stored on the keychain. Therefore, you will be prompted for your password after you upgrade to 10.0.7 and launch the application for the first time. If you choose to remove an existing version and then install 10.0.7, then the user will be required to reconfigure the client. This is not a change in behavior. However, for reasons stated below, we recommend you upgrade over your previous version of the Verse application. Note that the same applies when upgrading from the IBM ToDos application to the HCL ToDos application (when available).
The device ID generated by iOS will change (clients managed by IBM Maas360 and MobileIron are not affected). Moving to the HCL account caused a change in the development team ID for the IBM Verse application. This team ID is input to the Apple API that the application uses to generate a unique device ID. The result is a different device ID which will be used when communicating with the Traveler server (in the form HCL_IOS_xxxxxxxxxx). After installing 10.0.7, the client application will look like a new device to the Traveler server. You can see your new device ID on the About screen under Verse settings, the user’s Traveler home screen or in the Traveler Administration view.
A new device ID will have the following effects:
After you install 10.0.7 (either new or as an upgrade), the device will re-sync because Traveler treats the device as a new device because of the device ID change. You will see all mail in the all folders disappear and then start to re-populate. There is no way to avoid this re-sync, so plan accordingly.
A new profile document will be created for the new device ID (HCL_IOS_xxxxxxxxxx) by the Traveler server. This means all your preferences (things like days to sync, signature, etc) will be set to the defaults. However, if you take the recommended approach of upgrading (installing 10.0.7 over the top of a previous version), the Verse application will recognize the previous install and push all of your local preferences up to the server so that the new profile document is populated with your device preferences rather than the defaults.
If device approval is enabled on the Traveler server, the IBM Verse client may need to be re-approved depending upon the automatic approval settings.
The old device id (IBM_IOS_xxxxxxxxxx) will appear in the user’s device list until it is either reaped by the Traveler Server due to inactivity or deleted by the Administrator
The user may see duplicate notifications on the device for a period of time, typically 24 hours from the upgrade, because both the old and new device IDs are active on the server. There is no way for the new application to tell the server to stop sending notifications for the old device ID. After that period, the Traveler server will mark the old device as offline and stop sending notifications to the old device ID.
IBM Verse for Android is not affected by this change.