|
Bug #
|
Problem description and Symptoms
|
Workarounds
|
|
8026303
|
iPad (also iPhone): Several Applications prohibit Lotus Notes Traveler profile generation and download. Known Apps: Web Projector (which fixed their App in an update); FileApp, DownLoader, AirSharing, FTPReader, Mover+, USB Disk
THIS HAS BEEN FIXED ON iPhone AND iPod 4.1 IN THE TWO APPS WE TESTED SO WE PRESUME FIXED FOR ALL APPS ON THESE TWO DEVICES BUT NOT YET FIXED ON iPad AS OF 3.2.2.
|
Creating an account manually
1) If possible, uninstall the offending application, reboot the device and then install the Lotus Notes Traveler profile. The application can then be reinstalled.
2) Instead of using the profile to install Lotus Notes Traveler, the user could setup their device manually to talk to the Traveler server. Use the steps that are described in in the Lotus Notes Traveler 8.5.1 Information Center.
|
|
8298699
|
iPhone: Calendar List view shows calendar dates on wrong days.
FIXED in iOS 4.1.
|
None known
|
|
8308477
|
iPhone: Reschedule of monthly recurring events on device deletes first month and does not reschedule. Create a recurring monthly series on the server and let it sync to the device. Edit the event on the device and change the date of the starting event to the next day, Selecting "This and future events". The device puts the first event as the next day but does not reschedule the events.
|
None known.
|
|
8347870
|
iPad: (works on iPhone) 4 part name of email sender missing one part (middle name) in email display of FROM name.
|
None known.
|
|
8406447
|
iPhone: Embedded images in MIME mail displayed as HTML tags
|
Navigate to home screen, then back to the mail client and reopen the note to view the email. If that does not work, reboot the device and reopen the email.
|
|
8417352
|
iPod (also iPhone):Contact Birthday shifts one day when synced to Exchange server. Birthday field created on device in Contact is shifted back one day when synced to Exchange server. This problem is Timezone sensitive, and appears to occur only when the TimeZone on the device is East of GMT. Thus, the date was shifted when originally entered on the device set in Berlin, Germany but not when it was set in New York. The date for the birthday on the Server version of the contact is the day prior to the date on the device for the contact. The iPad does not seem to shift the day/time based on the device timezone offset from GMT but in general sends the correct day/month/year with the time being the current time of the device in GMT. In at least 1 case though (Japan timezone) the iPad sends the wrong day (1 earlier than what the user input).
|
|
|
8557523
|
iPhone and iPod: there is a loop in the provisioning process usually noticed when first upgrading from iOS3 to iOS4 which blocks the sync from starting. The loop is usually resolved but the time to resolve it is variable. We also refer to this as the "key 0" problem since the loop which causes the delay is a result of the provisioning key being set to 0.
|
None known. Usually resolves itself but may take a long time.
|
|
8925944
|
iPhone 3G and early iPod Touch devices cannot connect to the Lotus Traveler service on LotusLive Notes
This issue also applies to Lotus Traveler services where the authentication mechanism requires HTTP session cookies as part of its authentication scheme.
There is a known issue with Apple iPhone 3G and early iPod Touch models running iOS 4 that prevent it from using HTTP session cookies in the Exchange ActiveSync account. If you are using one of these devices that has been upgraded to iOS 4, and you are trying to connect to a Lotus Traveler service that requires HTTP session cookies, such as LotusLive Notes, then the device will fail to connect to the service. After manually configuring the account or installing a profile, when you open the Inbox or other folder in the mail application, you will see the generic error "Cannot Get Mail : The connection to the server failed.".
Further examination of network traces would show that the Apple device is making its request without the requested session cookie and instead there is a header in the data named X-Bad-iPhone-No-Cookie.
|
Contact Apple support for a profile that can be installed to enable HTTP session cookies for the Exchange ActiveSync account.
|
|
9242966
|
If cookies are enabled and the Apple is configured with two different user accounts talking to the same server, the Apple may send the cookie from account 1 on the request for account 2 and vice versa. This can also happen if account 1 is deleted and then account 2 is created before the cookie has expired.
FIXED in iOS 5.0.
|
Two possible workarounds:
1. Disable cookies in the HTTP server.
2. Setup one account using the server name (probably the account installed with the Profile). Setup the second account manually and use a different server name (for example, the ip address) instead.
|
|
9598038
|
Some PDF attachments are displayed as blank/all gray. The same attachments synced at other times or by other users may display correctly.
|
None.
|
|
9736766
|
Long display names for a mail sent from on a Korean language Apple device are not delivered because the address has been truncated and is incorrect.
|
None.
|
|
10426132
|
Simplified Chinese display names on mails sent from an Apple device will be improperly encoded if the device tries to use the GB2312 encoding. This will cause the normally cause the display name to contain corrupted characters.
|
Traveler implemented a work around for this in APAR LO66047.
|
|
10463718
|
Local search results are cleared in the Mail app search results using "All" once server results are returned. The search is left with "No Results Found on Server". If using "From", "To", or "Subject" to filter the search, the local results are still displayed. Only when using "All" as the filter do the local results get cleared after the server search is completed.
|
None.
|
|
10663624
|
An All-Day yearly repeating event in the Sydney, Australia time zone may show as 2 days on some instances on the Apple iOS 5 devices. The data is correct in Notes/Domino and is just a display issue in the Apple Calendar app.
|
None.
|
|
10896652
|
Exchange ActiveSync cookies are tied to Safari's cookie settings on the Apple iOS 5 devices. This results in increased authentication load on the server as cookies may be ignored. If the cookies are required to connect to the server (for example, LotusLive or other HTTP proxies that use cookies to track required state), then the syncs will fail.
|
On the Apple iOS 5 device, enable cookies in General - Safari - Accept Cookies and reboot.
|
|
10904453
|
After a folder is renamed on the Apple iOS 5 device, moving a mail in and out of the folder causes the folder to show multiple versions of the same mail instead of just one. This also applies after the folder is renamed when a mail is changed (for example, a read/unread change) on the server and is synced as an update to the device in that renamed folder.
|
Navigate out of the folder, open another folder (for example, Inbox), and navigate back to the original folder. Rebooting the device is another workaround.
|
|
11140665
|
After searching personal contacts (not the corporate directory but just the contacts already synced to the device), the Contacts app will send updates for all the matching contacts to the server although the contacts have not been updated by the user. It appears that this only happens when the Contacts app is opened the next time (while still displaying the previous local contact search results), but there might be other times where it does a Contact sync that may also cause this problem. If the server cannot process all of the updates (there could be hundreds or thousands depending on how many results matched the search) before the device times out the request, the contact sync will be stuck and not succeed again. If the server can process all of the updates (which do not really have any changes), then this will probably not be noticed; it is only an issue when the number of updates takes too long to process.
|
To avoid hitting the issue, clear the search results before leaving the contacts application. If encountered, remove the account (Apple profile or manual) from the device and reinstall the account.
|
|
11156094
|
The Apple calendar may show extra calendar instances for repeating meetings using the time zone for Israel. If the calendar event starts before the end of the 2011 daylight savings time (DST) end date and repeats with instances beyond the 2012 DST begin date, there are instances shown when they should not be. This results in duplicate events or deleted events being shown in the Calendar app but not in Notes.
|
Modify the entire event in Notes to use the 2012 Israel time zone values. Split any events that start before the end of the 2011 Israel DST end date.
|
|
11299535
|
The Apple device is not enforcing the specified "minimum number of complex characters" security setting when specified by the server.
|
The Apple device requires alphanumeric to also be enabled for the minimum number of complex characters to apply, so you must enable alphanumeric as well.
|
|
11424995
|
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 (normally 3 repetitions) before prompting the user to correct the password. If the user does not respond, the device will periodically try again (normally 4 repetitions per) and prompt the user again each time. In the end, the device has made multiple HTTP requests which may trigger some HTTP lockout logic for failed password attempts and the user may have multiple prompts on the device to dismiss in sequence.
|
Try to avoid the HTTP 401 in the first place by using the following steps.
Note: If you have more than one device, follow these steps for each device but make sure that you perform step 1 on all of the devices before performing steps 2-4. Otherwise, you 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 Lotus Notes Traveler login password per your password change procedures.
3. On your Apple device, set the password in your Lotus Notes Traveler account to be your new Lotus Notes Traveler login password. Be careful typing this password in, as you do not get a chance to confirm it. Select Settings > Mail, Contacts, Calendars > IBM Lotus Notes Traveler > Account Info > Password, and make the change.
4. On your Apple device, disable airplane mode. Select Settings -> Airplane Mode -> OFF. Re-enable WiFi if necessary.
|
|
11791433
|
Multiple reschedules of a repeating meeting on the device may cause events to have incorrect instances. For example,
1. Create a weekly meeting starting on April 4, 2012 and ending June 6, 2012.
2. Reschedule the 4th instance (4/25) to Thursday (4/26). "Save for this event only".
3. Reschedule the 2nd instance (4/11) to Tuesday (4/10). "Save for future events".
4.
Error: 4/24 now exists when it should not.
|
None.
|
|
11796974
|
Replies or forwards to mails with images may be missing some or all of the images.
|
None.
|
|
11850077
|
After the folders are resynchronized from scratch, the iOS device may use the older folder ID's on subsequent syncs and fail. Often, this will appear as a failure when moving mail from one folder to another because the target folder ID does not exist as it is the old ID instead of the current ID.
|
Remove profile for Traveler from the device and reinstall the profile.
|
|
12431367
|
Meetings for which the user is the chair appear on their iOS 6 device in light grey color instead of their correct calendar color. This only appears to occur if the logon name used to create the device sync profile contains a space.
|
Remove profile for Traveler from device and create new one using logon name that does not contain any space characters.
|
| 12951707 |
Processing (accept, etc) meeting notice from device Notification pop-up or directly from calendar may not work for iOS 6 and some iOS 7 levels. The device does not send the expected MeetingResponse flow to the server.
Processing notices from the device mail inbox or device calendar inbox queue should work as expected.
|
Fixed in latest iOS 7 and in iOS 8 levels. |
|
13088145
|
Calendar may stop syncing if the device encounters an error on the Exchange ActiveSync Provision command used to enforce the security settings on the device.
|
Reboot the device.
|
|
13053393
|
Rescheduling all instances of a repeating meeting to a different day of the week may cause events to have incorrect instances. Some of the instances may be deleted and the remaining instances will not be changed to the new day of the week.
|
None.
|
|
12848388
|
Try to read an e-mail and may see Loading... symbol for an extended period of time. Eventually the mail will load. This happens when trying to load a mail while the device is in the middle of syncing other mails to the device. This is more common for users who get a lot of mail every day. It is very common when a user first connects a device until the device has finished the first initial sync of all calendar, contacts and mail data.
|
None.
|
|
13235522
|
For some emails, the mail is rendered with the inline images either shown as generic icons or missing rather than rendered.
|
Navigate to another mail and then return to this mail. If that doesn't work, reboot the device.
|
|
13235622
|
When typing in text to reply to a message, the text does not get wrapped such that the whole text is not visible making composition more difficult.
|
None.
|
|
14229974
|
iOS change time for all occurrences, last instance lost on device.
Rescheduling all instances of a repeating event causes the last instance of the event to be removed from the device calendar of the chair.
All the instances are correct in the users Notes calendar.
|
Causing Traveler server to sync the calendar event back to the device will restore the missing entry to the device calendar. This can be done
by modifying the event in Notes or forcing the device to re-sync calendar by turning Calendar sync off and back on via the device account settings.
|
|
14230242
|
iOS6 unable to reschedule yearly appointment occurrence
Changing the time of an instance of a yearly repeating event from an iOS 6 device may result in the error "Alert Time. The event repeats before the alert occurs".
|
Change Alert value on device for the event to either "None" or "At time of event".
|
|
12132391
|
iOS removes invitee from single occurrence affects other occurrences
Removing an invitee from an instance of a repeating event removes the attendee from all instances of the event.
|
None
|
|
14229890
|
iOS 6: single delete removed all repeating entrees
Declining all instances of a previously accepted event on an iOS 6 device may result in some instances of the event remaining on the device calendar.
All instances are correctly removed from the Notes calendar. The instances that remain on the device calendar are instances the attendee has modified in some way. Typical example is user changed some instances to "Maybe" from "Accept" state.
|
Decline any remaining instances on device separately.
|
|
14229548
|
iOS: reschedule 1 occurrence of yearly meeting, all future occurrence lost
Rescheduling a yearly repeating event from the device using 'Save for future events" option causes all future instances after the selected instance (instance the change was made from) to be removed from the device and Notes calendar.
|
None
|
|
|
iOS meeting updates: SEVERE notice has no recipients, not sent.
When rescheduling or updating a repeating event, invitees may not receive the all the necessary Notices for the event change. The Traveler severe message "Notice has no recipients, not sent" appears on the server console when this happens. The scenario appears to occur to repeating meetings that have prior updates to attendees (added/removed) along with prior reschedules to some of the same instances. The device ends up sending a meeting notice with an invalid
UID value as part of making a "save for future events" modification.
Sample scenario:
On device create a monthly meeting (10 occurrences) inviting UserA
On device chair opens the 4th instance and adds UserB (this instance only)
On device chair updates the 5th instance and removes userA (save for future events)
On device chair updates the 3rd instance and changes location (save for future events)
** The notices generated by device to update the 4th instance after this last step are invalid.**
|
Do not enable "Save for future events" support in Traveler for iOS devices. See Traveler notes.ini setting NTS_AS_ALLOW_MEETING_SPLIT (Traveler 9.0.0.1 and later).
The default value is false which will cause Traveler to reject "Save for future events" changes from iOS device unless the selected instance is the first instance (all instances case).
|
|
14229656
|
Run-time exception after iOS recurring meeting reschedule
Rescheduling a repeating event using option "Save for future events" may incorrectly send Cancel notice for some instances of the event. When exception instances exist for an event the device may send an event update that includes both an update and a delete to the same exception instance when a "Save for future events" change is done from the device. A cancel notice for this instance delete is sent by the device resulting in instance being cancelled on attendee calendar. The Traveler server attempts to detect this scenario and not send the cancel notice to the attendee(s).
Sample scenario:
1) On device create a 3 day repeating meeting
from 9-10 am.
2) On device chair reschedules 2nd instance to
1-2 pm.
3) On device chair reschedules entire meeting
from 1st instance to 10-11 am using
"Save for future event" option.
4) result:
Device sends cancel notice for 2nd instance.
|
Avoid using "Save for future events" option for event changes on the device
|
|
15131408
|
Traveler Companion is unable to look up server contacts on iOS 7.
|
None. Must enter email addresses manually when composing a message in Companion if the address is not present in the list of contacts on the device.
|
|
15592963
|
Using iOS 7 w/Traveler 9.0.0.1 or 9.0.1 versions to take meeting notice action (accept / tentative) from device. If action button you select is already highlighted then the device will not send appropriate info to the server for processing. The device calendar will have latest info but the server Notes calendar will not.
|
Select the non-highlighted action button. The server will be updated accordingly. So 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.
|
|
15200645
|
Send mail from iOS 7 device and the mail is never sent.
To the end user the mail appeared to send, but the mail is completely lost, it does not show in Outbox or Sent Folder and recipient never receives the mail.
|
Most users report simply powering off then back on the device seems to prevent future occurrences. Some users reported having to remove then re-add the mail account on the device before the problem was resolved.
|
|
15691826
|
iOS 7 devices that fail sending a mail (new message, reply, or forward) may cause duplicate messages to be sent to the recipients.
|
If the mail is opened in the Outbox after the failure to send again, it appears to get a new ClientId marking it as unique from previous messages. If the mail gets sent without going into the Outbox, it appears to keep the ClientId such that any duplicates can be discarded as designed in the Exchange ActiveSync protocol by the server. Therefore, a possible work around is to wait for the automatic retries (if any) or manually sync the Inbox without going into the Outbox to resend the messages.
|
|
15708414
|
On iOS 7 devices, messages in Outbox not automatically resent.
|
Manually open the Outbox, select the message, and send it.
|
|
16011776
|
Downloading of attachments showing status over 100%
|
None.
|
|
16011799
|
A particular table in a mail is not rendered correctly on iPhone (iPad displays the same table correctly).
|
None.
|
|
16431803
|
Attachments do not display properly on iOS 7.1 devices when the devices use the Exchange ActiveSync command GetAttachment to get the data. The attachment will download but when displayed, it may show a black screen, gray screen, placeholder application message, etc. rather than the expected content.
|
In Exchange ActiveSync, there are multiple protocol levels. All of the levels support GetAttachment. In Exchange ActiveSync levels 14.0 and later, the ItemOperations command was added which can do the same thing as GetAttachment but in a different way. The bug in the device appears to be specific to GetAttachment, so if the device uses ItemOperations, the attachments are correct. Traveler 9.0.0.1 added support for Exchange ActiveSync 14.0 and later, so when the device is talking to those servers, it will use ItemOperations instead of GetAttachment and work properly. Therefore, a workaround is to upgrade your server to at least Traveler 9.0.0.1.
|
|
16867546
|
Unable to delete e-mail on an Apple iOS 7 device when offline. Often the user will not know they are offline and there is no error message or warning displayed. It may appear the item is deleted, but it will still be seen in the folder view.
|
This only seems to happen when offline and deleting the mail by selecting the Trash Icon from the mail view UI. Swiping the mail from the folder view and selecting Delete works when offline. Using the Trash Icon when connected to the Notes Traveler server works fine as well. The device simply is not allowing delete via Trash Icon when not connected to the server.
|
|
16915780
|
Apple iOS 7.1 and later levels will refresh sync folders too often. The device requests a folder sync, the sync happens but contains no folder changes, and the device resets the folder sync to start over. Prior iOS levels do not exhibit this issue.
|
Workaround for some known cases of this issue available in Traveler via APAR LO80340.
|
| 17363941 |
On Apple iPad running iOS 7.x unable to add Comments to Organizer for an existing meeting in the Calendar Application. |
Clicking on the field does not give focus to that field and pop-up the keyboard as expected.
Workarounds include:
1) Try rotating the iPad from portrait to landscape or vice versa.
2) Try soft reset of the device. Hold power and home key for 10 seconds, then power the device back on and re-try. |
| 17624505 |
Exchange ActiveSync mail Sync with command Change does not update the Subject or Body of the mail. |
If Traveler were to use the Change command, you would see this problem. To work around the issue, IBM Notes Traveler replaces one operation (Change) with two (Delete and Add). By doing this Delete+Add, the device correctly reflects the updated content, but it does introduce a timing gap between the Delete and Add where the item doesn't exist. If the device tries to perform some other operation between the Delete and Add (for example, a move to another folder which is an asynchronous Exchange ActiveSync command (MoveItems) from Sync), the operation will fail. However, once the Add completes, the operation should succeed if retried, so just retry the operation. The size of the timing gap will depend on many performance factors, so the faster the system, the smaller the gap. Therefore, you can increase the gap by improving overall performance which most often involves upgrading to the latest IBM Notes Traveler release to get all the latest improvements. |
| 17960131 |
Mail delete via Trash icon while viewing mail fails |
This does not happen with all mails as other mails can be deleted with the Trash icon while viewing the mail. The workaround is to return to the Inbox and swipe on the mail to access Trash and delete it that way. |
| 18383561 |
Exchange ActiveSync calendar not shown in Calendar app after iOS 8 upgrade |
Turn Calendars off in Settings - Mail, Contacts, Calendars - Account, reboot the device by turning it off and on, turn Calendars back on in Settings for the Traveler account, and wait a few minutes to let the device resync the calendar data.
If that does not work, repeat the same steps but instead of rebooting the device by turning it off and on, reboot by holding the home and power buttons until you see the silver Apple logo.
If that does not work, remove the account (most often, the profile that contains the account), reboot by holding the home and power buttons until you see the silver Apple logo, reinstall the account, and wait a few minutes for all the applications to resync.
|
| 18586613 |
iOS 8 device removes Location field on update to server.
Scenario: Owner of event updates Location field from iOS 8 device. Owner then updates the event again from the device but does not modify the Location field. On this 2nd update the device discards the Location information. Location field is now missing from device and server.
If the event is a meeting then the attendees no longer have the Location information as it is missing from the meeting update/reschedule notice.
|
Traveler APAR LO82292 includes workaround for iOS 8 devices to keep server Location value if no Location field is provided by the device update. APAR limitation is that an iOS 8 device user cannot delete the Location field from the device since the server will restore it. Traveler cannot determine whether the device bug deleted the Location field or the user intended to delete it. |
| 18652642 |
iOS user creates event on device and includes data for the Notes (Body) field. The body data does not sync to the user's mail database. |
iOS 8 device is not sending the Notes field to the server on an event Add. Workaround is to add the Notes field information to the event as an update after the initial add of the event. User could also create the event from Notes Client / iNotes instead. |
| 18853016 |
iOS loses repeat instance on device after accepting reschedule notice for the instance via Notes, iNotes, or other device. This is normally associated with a change of day only, no other fields changed (time, location, subject, etc not changed by notice).
The issue does not occur if notice is accepted from the iOS device unless you have multiple iOS devices, in which case the other iOS device(s) will still experience the issue.
|
Workarounds include:
1) Accept notices from the iOS device.
2) Resync calendar once problem is noticed by turning off calendar sync from iOS device and then turning back on.
3) Turn off Traveler calendar ghosting via notes.ini. Add NTS_IOS_CALENDAR_07=false to notes.ini for Traveler servers. This will not prevent the problem but will cause the underlying ical scenario to occur less often. This is not recommended unless users are running latest iOS 8.x on their devices. iOS 7.x users could experience problems accepting reschedules from the device where accept button is already highlighted on device even though the notice has not been accepted. Workaround for that side effect is to use the non-highlighted button (use tentative if accepted already highlighted).
|
|
19176737
FIXED in iOS 8.3
|
iOS 8.1.x displays extra week for All Day events that have weekly repeat rule with more than 1 day of the week included. Example: All day event for 1 week on Monday and Tuesday. The device calendar will display event on Monday and Tuesday for 2 weeks instead of 1 week. |
Workaround is to try and avoid weekly rule for All Days events with more than 1 day of the week included. This is not that straightforward since Traveler may send weekly rule to device even if the weekly rule is not used to generate the initial event. Generally if you use a daily or month by date/day rule to generate the all day event and the event does not include the same day(s) of week from more than 1 week in the month then the bug can be avoided. |
| 20733737 |
iOS 8 may not delete instances from device when they are deleted from server. Example:
User creates repeating appointment (daily for 5 days) via Notes.
Edit event in Notes and change location of 2nd instance.
Edit event in Notes and change location of 2nd instance again
Above changes sync fine to device User deletes 1st and 2nd instances from calendar via Notes
Only 1st instance is deleted from device
|
Workaround is to force calendar to resync by turning calendar sync off / on from the device.
APAR LO84144 has been opened to create workaround within Traveler such that Traveler will sync a delete then an add to device for any changes to an appointment instead of a change sync.
|