Known bugs with Apple devices and HCL Traveler

There are known issues using Apple devices with HCL Traveler that have been reported to Apple support.

The following tables show all bugs associated with Apple devices and HCL Traveler, organized by category.

Table 1. Account setup
Problem description Workarounds/More information

Fixed by Apple release

Apple iPad devices running Apple iPadOS cannot be identified as iPads because they use the same User-Agent strings as Mac laptops by default. When not identifiable as an iPad, the Traveler Home Page will not highlight the links to download the Verse client for Apple from the app store or generate an Apple Profile for Apple Mail, Calendar and Contacts apps. However, being an unidentified device causes Traveler to give all of the client links, so the link is still present on the page and the user just has to pick the correct link from all the links instead of from just the two iPad links. (FB7404681) Turning OFF Settings > Safari > Request Desktop Website > All websites will cause the iPad User-Agent to be used again, but this impacts all web sites, not just the Traveler Home Page. iOS 16
When the Apple device receives an authentication challenge (HTTP 401 response) due to a wrong user or password, the device will repeat the request multiple times before prompting the user to correct the password. If the user does not respond, the device will periodically try again and prompt the user each time. Because the device is making multiple HTTP requests, it may trigger an HTTP lockout due to failed password attempts and the user may have multiple prompts on the device to dismiss in sequence. (11424995)
Note: If you have more than one device, follow these steps for each one but ensure you perform step 1 on all devices before performing steps 2-4. Otherwise, you will lock yourself out on the second device.
  1. On your Apple device, enable Airplane mode so that all WiFi and phone data connections are turned off. Select Settings > Airplane Mode > ON.
  2. On your computer, change your HCL Traveler login password using the password change procedures.
  3. On your Apple device, set the password in your HCL Traveler account to your new HCL Traveler login password. Be careful typing this password, as you do not get a chance to confirm it. Select Settings > Mail, Contacts, Calendars > HCL Traveler > Account Info > Password, and make the change.
  4. On your Apple device, disable Airplane mode by selecting Settings > Airplane Mode > OFF. Re-enable WiFi if necessary.
Not fixed
Some Apps prevent the generation of HCL Traveler profiles, and/or the download of the Traveler App itself.. Known Apps include: FileApp, DownLoader, AirSharing, FTPReader, Mover+, and USB Disk (on iPad only), but there may be more. (8026303)
  1. Uninstall the offending app and reboot the device.
  2. Install the HCL Traveler profile, then reinstall the app.


  3. Instead of using the profile to install HCL Traveler, setup the device manually using the information in How do I create an account manually? .
iOS 10.1
The Apple device does not enforce the specified Minimum number of complex characters security setting when specified by the server. (11299535) The Apple device requires alphanumeric security to also be enabled for the minimum number of complex characters to apply. Ensure alphanumeric security is enabled as well. iOS 10.1
After searching personal contacts (not the corporate directory), the Contacts app will send updates for all matching contacts to the server, although the contacts have not been updated by the user. This issue only occurs when the Contacts app is opened while still displaying the previous local contact search results. If the server cannot process all updates before the device times out the request, the contact sync will fail. If the server can process the updates before a timeout, then the issue will likely not occur. (11140665) Clear the search results before leaving the contacts application. If you encounter the issue, remove the account (delete the Apple profile or manually remove the account) from the device and reinstall the account. iOS 10.0.2
Table 2. Mail
Problem description Workarounds/More information Fixed by Apple release
The Apple iOS/iPadOS 16.x Mail app no longer sends a text/plain part when replying to or forwarding a message. Any mail clients that display the text/plain content (some mail applications only display text/plain content and not text/html content, the Mail app uses the text/plain for the Preview text, etc.) will no longer have the proper text/plain content to display and may display unusable text instead. (FB11745983) A workaround to generate and insert a usable text/plain part on behalf of the client is included in Traveler Not fixed.
Mail with a display name containing brackets does not show the brackets nor the text within the brackets. (FB9788909) None. However, this appears to be cosmetic only as replying to or forwarding the mail does contain the missing brackets and text. Not fixed.
Apple iOS/iPadOS 15.0 and later: After disabling and re-enabling mail sync, messages in the Mail app may not be displayed. (FB9631099) Force close and reopen the Mail app or restart the device. Not fixed.
Apple iOS/iPadOS 13.0 and later: When you search for messages, you may see only partial results. After disabling and enabling mail sync or increasing the number of "Days to sync", search finds only newly received messages. Note that a search request is performed locally against the mail content on the device. The Traveler server is not involved in the search processing. (FB7401498) A consistent workaround has not been identified. Performing a reset at the Traveler server can help by forcing the client to rebuild its search index. Not fixed.
Inline images may not display in the Mail app. The problem persists even after navigating to another mail message and returning, as well as after terminating and restarting the Mail app. (35394005) None. iOS 16
On Apple iPhones, embedded images in MIME mail display as HTML tags. (8406447) Navigate to the Home screen, then back to the mail client and reopen the note to view the mail. If that does not work, reboot the device and reopen the mail. iOS 16
Simplified Chinese display names on mail sent from an Apple device will be improperly encoded if the device tries to use the GB2312 encoding. This causes the display name to contain corrupted characters. (10426132) HCL Traveler implemented a work around for this in APAR LO66047. 11.4.1
Replies or forwards to a mail message containing images may be missing some or all of the images. (11796974) None. iOS 16
When reading mail, the Loading... symbol may display for an extended amount of time before the message loads. This occurs when trying to load mail while the device is syncing other mail. This issue is more common for users who get a large amount of mail every day. It is very common when a user first connects a device, during the first initial sync of data. (12848388) None. Not fixed.
Mail may render with the inline images either shown as generic icons or missing completely, rather than rendered. (13235522) Navigate to another mail message and then return. If that fails, reboot the device. Not fixed.
Mail may render with inline images for document links as generic icons rather than rendered (FB7670498) Navigate to another mail message a couple of times. If that fails, reboot the device. Not fixed.
Apple iOS 7.1 and later: Levels refresh sync folders too often. When the device requests a folder sync, even though it contains no folder changes, the device begins the sync again. (16915780) A workaround for some cases of this issue is available for HCL Traveler with APAR LO80340. 12.0
Syncing Exchange ActiveSync mail with the Change command does not update the Subject or Body of the mail. (17624505) In this issue, HCL Traveler replaces the Change operation with the Delete and Add operations. As a result, the device correctly reflects the updated content, but it introduces a timing gap between Delete and Add where the item does not exist. If the device tries to perform another operation between the Delete and Add (for example, a move to another folder), the operation fails. However, once the Add completes, the operation should succeed if retried. The size of the timing gap depends on performance factors, so the faster the system, the smaller the gap. Therefore, you can decrease the gap by improving overall performance, which most often involves upgrading to the latest HCL Traveler release to get all of the latest improvements. Not fixed.
Folder names display as a random hexadecimal value, rather than the actual, readable name (10463402) At times, where the readable folder name should be displayed at the top of the view, some combination of alphanumeric text displays instead. This appears to be some sort of internal ID rather than the name. For example, instead of "Personnel", you see "70FB9178-576E-4CA-A08E-....". This issue has existed going back to to iOS 5. Not fixed.
Inline images in the Mail app show as white boxes until the app is restarted. (31173739) Terminate and restart the app. Not fixed.
Name lookup results do not display on the device, even though Traveler is sending results. (29045165) When a Native Apple Mail user on a Traveler Server begins a new message and types part of the recipients name, the name lookup on the device returns nothing, even though the server has sent down multiple results using XML. iOS 16
When a native Apple Mail user on a Traveler Server attempts to compose a new messages and types part of the recipients name, the name lookup on the device returns nothing. (29045165)

Try the search on the device again by deleting and retyping the name.

iOS/iPadOS 13 and up waits for 4 characters to send the name lookup.
Not fixed.
Apple iOS/iPadOS 13.0 and later: After sending one email from the Mail app, two copies of the email appear in the Sent folder. (FB7337231) As of iOS/iPadOS 13.0, Apple devices add an extra entry to the Sent folder for any email 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. iOS 13.3
Apple iOS/iPadOS 13.0 and later: Choosing to save a mail to the Drafts folder (Cancel > Save Draft), the saved draft mail cannot be found in the Drafts folder. There is no indication of an error and the draft mail content will be lost. (FB7345257) None. iOS 13.3
Local search results are cleared in the Mail app search results using "All" once the server results are returned. The search displays "No Results Found on Server". If using "From", "To", or "Subject" to filter the search, the local results are still displayed. It is only when using "All" as the filter that the local results get cleared after the server search is completed. (10463718) None. iOS 9
Starting in iOS 7.1, attachments do not display properly when the devices uses the Exchange ActiveSync command GetAttachment to retrieve the data. The attachment will download, but when displayed, it may show a black screen, gray screen, or placeholder application message, rather than the expected content. (16431803) Upgrade your server to at least HCL Traveler 9.0.1. iOS 10.1
Some PDF attachments are displayed as blank/all gray. The same attachments synced at other times or by other users may display correctly. (9598038) None. iOS 10.1
Long display names for mail sent from a Korean language iOS device are not delivered because the address is truncated and incorrect. (9736766) None. iOS 10.1
When replying to a message, the text does not wrap at the edge of the screen and is not visible in its entirety, making composition more difficult. (13235622) None. iOS 10.1
Starting in iOS 5, after a folder is renamed on the device, moving mail in and out of the folder causes it to show multiple versions of the same mail instead of just one. This also applies after the folder is renamed when mail changes (for example, a read/unread change) on the server and is synced as an update to the device in that renamed folder. (10904453) Navigate out of the folder, open another folder (for example, the Inbox), and navigate back to the original folder. If this does not work, reboot the device and try again. iOS 10.1
Tables in mail messages are not rendered correctly on iPhone. However, iPad devices display the same table correctly. (16011799) None. iOS 10.1
Starting in iOS 7, problems are encountered when deleting mail on the device when offline, and there is often no error message or warning displayed. It may appear the item is deleted, but it will still be seen in the folder view. (16867546) This issue only occurs offline when deleting mail by selecting the Trash icon from the mail view. The issue is not present when swiping the mail from the folder view and selecting Delete, or using the Trash icon when connected to the HCL Traveler server. iOS 10.1
On Apple iPads, mail sender names which contain a middle name in the FROM line are missing the middle name. (8347870) None. iOS 10.1
Deleting mail using the Trash icon fails. (17960131) The workaround is to return to the Inbox, swipe on the mail item, then use Trash function. iOS 10.1
Attachments on a mail message are corrupted when the mail is forwarded on iOS 9.3.1 devices (26687880) None. iOS 10.1
Table 3. Calendar
Problem description Workarounds/More information

Fixed by Apple release

Changing an all-day, yearly repeating event to the previous day causes the following Apple alert: "Another instance of this event occurs on this date". This prevents the user from rescheduling the event to the previous day. (FB9340589) Use a Notes or Verse client to reschedule the anniversary instead of the iOS Native Calendar. iOS 16
Starting with iOS 12.0, the Apple device calendar application will not allow you to add an attendee to a meeting from the device if the attendee's internet email address contains an '=' character (FB8834742). The problem only applies to adding an attendee to a meeting from the device. Attendees with an '=' in their internet address can be added from other clients and will sync and display on the Apple device calendar meeting correctly. For Domino users that do not have an internet email address, HCL Traveler defaults to generating an encoded internet address for use by the device. This generated internet email address often contains '=' characters which will cause the device calendar application to not allow these users to be added to meetings from the device. Not fixed.
Updates to a calendar reminder/alarm for a repeating instance from the iOS Calendar app may not get saved. (FB8834949) For repeating meetings, iOS devices may not send an update to the server when a user updates the reminder/alarm for an instance of the meeting. The device used for the action shows the change, but the server and other devices are not updated. If the event is resynced back to the device, it overwrites the change and shows the server value. Not fixed.
Changing a repeating event to a non-repeating event from the iOS Calendar app may result in multiple instances of the event left on the calendar. The first instance of a repeating event will always remain on the calendar even if it is converted to a non-repeating event. If another instance (not the first one) was selected when the change was made, that instance will also remain on the calendar.
Note: Changing a repeating event to non-repeating event is no longer allowed by iOS/iPadOS 14 and later.
Not fixed.
Calendar entries with a location may display a map of 0,0. (50905339 and technical support incident 715448814) A severe iOS bug exists that prevents updates to an event's location if the device previously attempted to display a map of the location. To prevent the device from doing that, Traveler sends empty coordinates and the device instead displays a map of 0,0. This allows the location to be updated normally, but the map cannot be removed. Not fixed.
Chair users cannot change multiple instances of a non-meeting event type (appointments, all day events, reminders, etc). (50021374) This is a workaround for changes to multiple instances of a repeating appointment or all day event missing key recurrence rule information from the device. Not fixed.
Rescheduling any instance of a repeating meeting by changing just the end time always uses the end time of the first instance. (48547272) This issue only applies if the end time is changed by itself. Changing the start time works as expected. The device sends the end time of the first instance no matter which instance was selected which can result in the meeting being rescheduled with the incorrect end time. Not fixed.
Device does not allow all-day events or anniversaries to be rescheduled to the following day if a reminder/alarm is set for the event. The user gets an error that the event cannot be moved to that date as if an instance of the event already exists on that date. The only workaround is to remove the alarm and then move the event, then the alarm can be added back successfully. Not fixed.
Removing a calendar reminder/alarm from the iOS Calendar app does not get saved. (FB6171108) For non-repeating meetings, iOS devices do not send an update to the server when a user removes a calendar reminder/alarm. The device the action was taken on will show that there is no reminder on the event, but the server and other devices will not be updated. If the event is resynced back to the device, it may overwrite the change and the reminder/alarm will appear on the event again. Not fixed.
Apple iOS/iPadOS 13 devices do not send meeting responses to the server if ghosting is disabled. (FB7328175) Responding to a meeting notice may not send the response to the server, causing the event to appear accepted on the device but not on other clients such as Notes.

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.
Not fixed.
Meeting invites generated from are synced to the device (webex.ics attachment), but when a user opens the attachment and performs an Add To Calendar action, the event appears on the user's device calendar but does not sync to the server. (29043233 and 27691361) Add ics invites using the HCL Notes client. Not fixed
The Calendar Inbox may have an extra/duplicate entry when an event is ghosted or every instance has been changed from the original. This extra entry may have the same data as another entry but may not be removed from the Calendar Inbox even after taking action (Accept/Maybe/Decline) on it. (29252221) Workaround included in Traveler 11 with Exchange ActiveSync 16 support. For earlier versions without Exchange ActiveSync 16 support, this issue may resolve if all other outstanding notices for the meeting are accepted. N/A
When the user creates a repeating monthly meeting for 5 months and makes multiple changes to instances 2 through 5, and then reschedules the first instance to a later date, all previous changes are lost.(30398937) Workaround included in Traveler 11 with Exchange ActiveSync 16 support. N/A
Canceling the first instance of a repeating meeting where an invitee was added later results in the meeting Cancellation notice only being sent to the original invitees. The invitee added after the meeting was originally created does not receive a Cancellation notice and the meeting remains on their calendar. (24188983) Workaround included in Traveler 11 with Exchange ActiveSync 16 support. N/A
The last instance of All Day repeating events may be missing on the device. This seems to occur when the device timezone has a value East of UTC (such as Berlin, Germany) and the RRULE sent to the device uses a COUNT of instances. The issue isn't present if RRULE uses the UNTIL date or if the timezone is West of UTC (such as New York, USA).(29974878) Workaround included in HCL Traveler version and higher. N/A
Repeating yearly all day events occurring in 2038 and later appear as two day events in the iOS calendar. (18398844) None iOS 14.0
After declining an instance of a repeating meeting, the other instances may be marked tentative. (25114211) Apple Bug 25114211 has been opened for this issue. The Apple device sends both the decline and tentative actions to the server, even though the user did not choose tentative for any instances. iOS 14.0
No notice is sent to the last invitee of a meeting when it is canceled using the iOS device. (20684754) Use Notes instead of an iOS device to remove the last invitee. iOS 12
Device does not immediately send decline action to the server. (48548937) Decline actions taken from the calendar may not send to the server right away (observed up to a 45 minute delay). Force closing and reopening the Calendar app should send the decline response right away. iOS 12.3
Chair cannot remove all invitees from a meeting. (47645099) After removing all invitees from an instance of a repeating meeting, iOS devices send an update that immediately adds all invitees back to the meeting. Removing all but one of the invitees works as intended. iOS 13
The location field is lost on the iOS device calendar when upgrading to iOS 10.2. What makes this issue unique is that the location field is only lost if it starts with a URL. For example, the location field contains This happens regardless of whether the user is the chair or an invitee to the event.(29853668) Location values are not lost from the server the device syncs with, only from the device. iOS 11.0
Removing an invitee from one instance of a repeating meeting removes them from all instances on iOS 10.2.1 (31067387 and 21448080) Do not remove an attendee using the iOS Native Calendar. iOS 11.0
Starting in iOS 9.2.1, when a meeting Chair creates a repeating event that includes Location information and then modifies the Location, the modified Location value is never sent to the Traveler server (25011200 and 23203433) None iOS 10.3.3
Starting in iOS 9.2, when a user declines a reschedule from the calendar, a Tentative response is sent instead. (25114211) None iOS 10.3.3
When rescheduling one instance of a repeating meeting from the device, all events in a recurring meeting may appear to have been rescheduled for all attendees. But no data is changed and they all continue to contain the correct information. (28779634) It is possible this occurs because the device is sending up two sendmail requests. The first sendmail contains only a rule, and the second only a recurrence ID. HCL Traveler Server only expects the second sendmail in a case like this. This issue does not occur when the reschedule is made from a 9.3.5 device. iOS 11.0
On an iOS 7 or later device, using on premises HCL Traveler or later, when the user takes actions on a meeting notice, such as Accept or Tentatively Accept, the action button the user selects may already be highlighted. In this case, the device does not send the appropriate info to the server for processing. This causes the device calendar to have the latest info but the server calendar does not. (15592963) Select the non-highlighted action button. The server will be updated accordingly. As an example, if Accept is already highlighted then use the Tentative button. This will put the event on your calendar as Tentative, but both the device and server calendars will be correct. If the Tentative button is highlighted, then use the Accept button. iOS 10.1
On an iPhone, embedded images in MIME mail display as HTML tags. (8406447) Navigate to the home screen, then back to the mail client. Reopen the mail message. If that does not work, reboot the device, and try again. iOS 10.1
The birthday field created on the device in Contacts is shifted back one day when synced to the server. This problem is Timezone sensitive, and occurs only when the Time Zone on the device is East of GMT. (8417352) For more information, see Apple contact dates (Birthday / Anniversary) off by a day. iOS 10.1
Removing an event instance from a recurring meeting removes all the instances on iOS 16. (FB10910783) Remove the event instance using a non-iOS 16 client (eg. Notes, Verse Web, iOS Verse, Android Verse, iOS 15). Not fixed.
Device does not allow repeating all-day events to be rescheduled on iOS 16. (FB10913494) The user gets an error saving the reschedule. Only workaround is reschedule using a non-iOS 16 client (eg. Notes, Verse Web, iOS Verse, Android Verse, iOS 15). Not fixed.
Note: Validation done with iOS 16 and higher connected to Traveler 12.0.1 FP2 (and higher) with Exchange ActiveSync 16 support.