Android

1.0.3.1, October 22, 2014


Hot fix to address a packaging issue, #308.

1.0.3, October 17, 2014


Some highlights from our latest quality release:

1.0.2, August 22, 2014


This is our second quality release for 1.0.0. As we continue to firm up our existing quality and performance while building toward enhancements and features, we've gone over and done a number of major improvements on our built-in test infrastructure including using a mockwebserver that better simulates "un"-happy network paths.

We also addressed a number of major behavior issues around replication, and purged or deleted documents, as well as our pluggable cookie-based auth support. More information regarding these highlighted functional fixes can be found below.

1.0.1, July 22, 2014


This is our first quality release for 1.0.0. Our core focus for this patch was to address immediate behavior correctness issues as well as an overall performance improvement around Attachment replication and LiveQuery updates.

1.0.0, May 21, 2014


This is our first official release for Couchbase Lite. A major change from our Beta releases and 1.0.0 is an expansion of our platform support, which includes a 1.0.0 ready version of "portable" Java libraries to support Linux-based app development. We've also made a lot of advancement in the performance stability of our Android and Java platform, created better parity for our authentication support, and enabled better logging for community debugging feedback. Simultaneously to this release, we have also published our first beta for our C# support in a collaborative effort with our partner, Xamarin.

There is a known security issue for Android PhoneGap/REST developers using API Level 17 and below. This issue is captured in the following issue: #48

There are known performance issues that we plan to fix before general release. These performance issues include slowness in replication and in view creation. These issues include the following: 123, 125, 126

This is a known issue that multiple updates to a single document within a single transaction will cause a conflict error. This issue is currently being reviewed and addressed in the following: 220.