On iOS 14.5 or later, finding BirdieSync server or resolving the server hostname could fail while trying to connect. At first time, a permission popup window will now be displayed asking authorization to access to local network.

- In some cases, alarm in recurring event with modified or deleted occurrence could be not synchronized to mobile device

- If several BirdieSync servers were simultaneously running on the local network, app could freeze when searching for BirdieSync hosts - If user cancelled the search for BirdieSync hosts, status was still displaying "Searching for BirdieSync host"

- Contact with notes could fail to synchronize - A contact whose instance message address was cleared could later fail to synchronize - Attendee email address is now synchronized as well as organizer - Save button in Settings window could be incorrectly greyed out - App no longer exits when going to background but connection with desktop server is automatically closed

- On iOS 11, the modification of a contact with an identical photo could lead to an unexpected error - The full height of the iPhone X is now used

- On iOS 11, enumeration of contacts could take a long time - Recurring event with occurrence moved outside the synchronization period could fail to synchronize

- Synchronization of contact with related name could lead app to exit - Synchronization of recurring event with a single occurrence and no recurrence rule is now supported

On iOS 10, app could crash at launch On iOS 10, app could display an unexpected error after connection to the server If a new contact was synchronized with no first name and last name and a phone number, it could lead to the creation of an empty contact

- A contact created without first name, last name and with a phone number could make the app crash - If an event couldn't be read during enumeration, the description of the event was not displayed in the error message on the server - iOS subrevision is now displayed in the log

After being synchronized locally or in iCloud, some specific contacts could be considered as modified again Synchronization of a contact in a group which has just been created could fail with an unexpected error

All day events leaving the synchronization period could be considered as deleted during synchronization

In some specific cases, events synchronized in iCloud calendar could be considered as modified at next synchronization Synchronization in an iCloud calendar could fail with an unexpected error If a unique calendar needed to be created and synchronized, synchronization of events could fail App could crash if an event could not be found Events with a recurrence end date are now better synchronized Event with a cancelled meeting status could fail to synchronize

BirdieSync could crash while creating Exchange contacts If app is not authorized to access to contacts or events, the error is now transmitted to the server Exchange calendars have now their type correctly transmitted to the server

Support of BirdieSync 3.0 Support of iOS 9.0 To synchronize with BirdieSync 2.x ensure that switch "BirdieSync server 2.x" is ON in BirdieSync app Settings.

Support of iPhone 6 display

Bug fix: If a recurring event with a modified or deleted occurrence was modified in Thunderbird and then synchronized, BirdieSync app could crash.

Bug fix: - After a first synchronization and remaining connected, the synchronization of a modified event in Thunderbird could lead to an unresolved item or a crash of BirdieSync app

It is highly recommended to install BirdieSync 2.4.9.0 on the PC Changes: - Performances of event synchronization have been improved. Bug fixes: - On iOS 7, if a high amount of events were synchronized, it could lead to a crash (requires BirdieSync 2.4.9.0 on the PC) - If an event could not be created on the iPhone, it could lead to a crash - Home and work emails, and instant message fields of Exchange contacts are now properly synchronized

- After the first installation, on iOS 6.x after the contact and event access authorization or in some other rare circumstances, an unexpected error could be displayed in BirdieSync on the desktop (the error would disappear after a relaunch of the app) - If iCloud calendar synchronization is enabled, new calendars are now created in iCloud and no longer locally. - Better support of iPhone 5 screen - Log file now keeps information of previous launches

- On iOS 6.0, if Iphone was not authorized to access to contacts and calendars, it could make app crash or leading to unresolved items. - If iPhone is connected to a Wi-Fi local network, when looking for hosts or resolving hostnames, IP address belonging to this network is now selected in priority - When expressed by Siri, contact birthday could be one day before the actual date. - To workaround a problem with yearly events in the SDK, if the recurrence end is an occurrence count, it is now converted to a limit date - For more security, ensure that a recurring event created on the iPhone has occurrences in the synchronization range, to avoid a deletion on the desktop at next synchronization. - If a recurring event was converted to a simple event on the PC, it still remained recurrent on the iPhone. - Due to Apple SDK evolutions, app can now only run on iOS 4.3 or later.

Bug fixes: - On iOS 6.0, app could crash when connecting to the desktop - If a recurring event had occurrences past the recurrence end date, app could loop when preparing event synchronization - If an error occurred during contact creation on the iPhone, it was not removed after having been marked unresolved. - App could crash when displaying an alert message in case of error - App could crash when opening settings for the first time

Installing this new version can lead to a resynchronization of contacts and events from the iPhone to Thunderbird. Bug fixes: - App could crash when synchronizing recurring events with modified occurrences from Thunderbird to the iPhone.

Changes : - Synchronization of iPhone calendars with Thunderbird and Lightning/Sunbird is now supported (since Thunderbird 12.0) - It’s now possible to find hosts with BirdieSync without having to enter a specific host address. - PC hostname can be used as host address in Settings. - In main window, the connection status is more detailed. - Error messages are more detailed in case of connection problem. Caution: Because of changes regarding the way the iPhone is identified, a new iPhone entry will appear in BirdieSync Activation tab on the PC, leading to a full resynchronization of contacts. Fixes: - BirdieSync could not connect with old desktop version (before Thunderbird 7.0)

Changes : - Synchronization of iPhone calendars with Thunderbird and Lightning/Sunbird is now supported (since Thunderbird 12.0) - It’s now possible to find hosts with BirdieSync without having to enter a specific host address. - PC hostname can be used as host address in Settings. - In main window, the connection status is more detailed. - Error messages are more detailed in case of connection problem. Caution: Because of changes regarding the way the iPhone is identified, a new iPhone entry will appear in BirdieSync Activation tab on the PC, leading to a full resynchronization of contacts.

Changes: - Compatibility with BirdieSync desktop 2.2.0.0 Bug corrections: - Application could crash while synchronizing particular contacts already present on the iPhone - Entering a hostname instead of an IP address in the settings made the application crash when connecting - If the hostname could not be resolved, no error message was displayed - In some rare circumstances, identical passwords set on the desktop and the mobile device could mismatch - The "File as" field in Thunderbird contact was emptied when the contact was synchronized from the iPhone