application-services/CHANGELOG.md

483 строки
24 KiB
Markdown
Исходник Обычный вид История

# Unreleased Changes
**See [the release process docs](docs/howtos/cut-a-new-release.md) for the steps to take when cutting a new release.**
2019-03-23 01:13:09 +03:00
[Full Changelog](https://github.com/mozilla/application-services/compare/v0.22.0...master)
# v0.22.0 (_2019-03-22_)
[Full Changelog](https://github.com/mozilla/application-services/compare/v0.21.0...v0.22.0)
## Logins
- Added a disableMemSecurity function to turn off some dubious behaviors of SQLcipher. ([#838](https://github.com/mozilla/application-services/pull/838))
- The iOS SQLCipher build configuration has been adjusted ([#837](https://github.com/mozilla/application-services/pull/837))
2019-03-22 23:33:59 +03:00
## Push
### Breaking changes
- `PushManager`'s `dispatch_for_chid` method has been renamed to `dispatchForChid`.
- `PushManager` constructor arguments are now camelCased.
## `org.mozilla.appservices` Gradle plugin
- Artifacts are now to be published to the `mozilla-appservices` bintray organization. This necessitates version 0.4.3 of the Gradle plugin. ([#843](https://github.com/mozilla/application-services/issues/843))
# v0.21.0 (_2019-03-20_)
[Full Changelog](https://github.com/mozilla/application-services/compare/v0.20.2...v0.21.0)
## General
- Breakpad symbols should be available for android now ([#741](https://github.com/mozilla/application-services/pull/741))
2019-03-18 19:31:21 +03:00
Bookmark APIs for iOS and Kotlin and implement them using the FFI (#743) * Define conversions to/from protobuf types * Define bookmark message types * Add method of getting 'shallow' tree info * Properly provide parent/position for items * Add the rust side of the Bookmarks FFI * Kotlin bookmarks FFI * Copy xcode project over from logins to start places ios ffi * places ios: C bindings for places * protobuf setup for places ios (and docs) * Fix some things that were annoying me about BookmarkRootGuid, and move it to it's own file * Add a bookmarks FFI function to return all bookmarks with the requested URL * Clean up leftover logins stuff in places ios * Implement swift bookmarks API * Fix bad comment and missing null check in kotlin bookmarks * Try and add places to the iOS megazord (hit issue with msg_types name collision) * Rename msg_types to be unique, finish integration with iOS megazord * Finish documenting how to pass protobuf data back and forth for swift * Comment tweak and change canEdit -> isRoot * Small tweaks to the swift API (some renaming, change class => struct, etc) * Don't require type in update (since it can't be changed), and handle errors better * Undo struct -> class change since it subtly broke things * Respond to feedback from justin * Allow requesting a only the first level of folder children * connUseAfterApiClosed -> connUseAfterAPIClosed * WIP iOS tests * Make iOS tests build * Improve path handling for iOS * Fix megazord test setup and document the weird testing steps that were needed * Fix failing iOS tests * Move protobuf-returning functions into their own file * Add searchBookmarks function * Use a sealed class and data classes in the kotlin API * Require that callers of getBookmarksTree pass in the root and whether or not to fetch recursively, rather than using the most expensive possible default * rename deleteBookmark => deleteBookmarkNode * Use InterruptScope in the reader bookmark methods * Fix rebase issue * Allow interrupt() on iOS * Use changes from #788 to make places xcode project build much faster * Change `extern` to `public`, use fewer protobuf types in the rust because they make testing it painful * More tests of new rust code * Expose relevant errors over the FFI, and document them (also, fix the kotlin doc formatting) * fix 'its' being wrong basically everywhere * Fix many doc typos * Use FfiStr in bookmarks * Fix doc nit * Make missing titles come through as '' for better API consistency * Tests for the rest of the new rust functions * Clarify doc nit * Changelog entry for bookmark ffi * Expose runMaintenance to Swift * Handle NoItem => NoSuchGuid * Rename places::storage::bookmarks::public to places::storage::bookmarks::public_node * Lina's review feedback
2019-03-19 18:41:19 +03:00
## Places
- Places now is available on iOS, however support is limited to Bookmarks. ([#743](https://github.com/mozilla/application-services/pull/743))
- Places now has bookmarks support enabled in the FFI. This addition is too large to include in the changelog, however both Swift and Kotlin APIs for this are fairly well documented. ([#743](https://github.com/mozilla/application-services/pull/743))
2019-03-18 19:31:21 +03:00
# v0.20.2 (_2019-03-15_)
[Full Changelog](https://github.com/mozilla/application-services/compare/v0.20.1...v0.20.2)
- An automation problem with the previous release, forcing a version bump. No functional changes.
- Local development: non-megazord builds are now `debug` be default, improving local build times
and working around subtle build issues.
- Override this via a flag in `local.properties`: `application-services.nonmegazord-profile=release`
2019-03-15 19:28:51 +03:00
# v0.20.1 (_2019-03-15_)
[Full Changelog](https://github.com/mozilla/application-services/compare/v0.20.0...v0.20.1)
- A error in the build.gradle file caused the v0.20.0 release to fail, this
release should not be meaningfully different from it.
2019-03-14 23:18:36 +03:00
# v0.20.0 (_2019-03-14_)
[Full Changelog](https://github.com/mozilla/application-services/compare/v0.19.0...v0.20.0)
## General
- The previous release had an issue with the megazords, and so another
release was needed. This is version 0.4.2 of the megazord plugin.
([#775](https://github.com/mozilla/application-services/pull/775))
### Breaking Changes
- All package names have been normalized. The gradle packages should all be
`org.mozilla.appservices:component`, and the java namespaces should be
`mozilla.appservices.component`. ([#776](https://github.com/mozilla/application-services/pull/776))
## Logins
### Breaking Changes
- The gradle package for logins has been changed from
`'org.mozilla.sync15:logins'` to `org.mozilla.appservices:logins`.
([#776](https://github.com/mozilla/application-services/pull/776))
2019-03-14 04:03:21 +03:00
## Places
### Breaking Changes
- Several classes and interfaces have been renamed after feedback from consumers
to avoid `Interface` in the name, and better reflect what they provide.
- `PlacesApiInterface` => `PlacesManager`
- `PlacesConnectionInterface` => `InterruptibleConnection`
- `ReadablePlacesConnectionInterface` => `ReadableHistoryConnection`
- `WritablePlacesConnectionInterface` => `WritableHistoryConnection`
- `ReadablePlacesConnection` => `PlacesReaderConnection`
- `WritablePlacesConnection` => `PlacesWriterConnection`
2019-03-14 23:18:36 +03:00
- The java namespace used in places has changed from `org.mozilla.places` to
`mozilla.appservices.places`
([#776](https://github.com/mozilla/application-services/pull/776))
- The gradle package for places has been changed from
`'org.mozilla.places:places'` to `org.mozilla.appservices:places`.
([#776](https://github.com/mozilla/application-services/pull/776))
## FxA
### Breaking Changes
- The gradle package for fxa-client has been changed from
`'org.mozilla.fxaclient:fxaclient'` to `org.mozilla.appservices:fxaclient`.
([#776](https://github.com/mozilla/application-services/pull/776))
2019-03-14 04:03:21 +03:00
# 0.19.0 (_2019-03-13_)
[Full Changelog](https://github.com/mozilla/application-services/compare/v0.18.0...v0.19.0)
## General
### What's New
- Initial support for the new Push component landed, however it's not yet ready
for widespread use ([#683](https://github.com/mozilla/application-services/pull/683))
2019-02-27 23:23:30 +03:00
Refactor places connection management (#718) * This is a proof-of-concept for how we might manage connections. It is currently in a good enough state to see if the idea is worth pursuing. At a minimum, and before landing, we'd: * split the schema.rs changes into its own PR - they aren't strictly needed for what this patch does. * Probably move PlacesAPI into its own source file, and better consider threading considerations - the PlacesAPI instance will end up being called from multiple threads (although the stuff we hand out shouldn't be) * Manage the "sync" connection similarly to how we manage the "write" connection. The PlacesAPI object is probably also where the sync "store" objects can live (as currently we create brand new stores each sync, which isn't as optimized as it should be) * FFI changes needed to support this - this would be a breaking change, but shouldn't be too difficult to manage. * Lots of other cleanup - I figured I'd get comments on the general approach before spending much time cleaning things up. So by all means, offer all suggestions, but the main thing I'd like from this is general approval that we should go ahead with this. * Flesh out the Api more, including the Kotlin side of the fence * First cut at Thom's feedback * Fix nit: IOError => IoError * Return writer connection to API when finished with it, ensure there's only one in kotlin * Avoid duplication of rustCall * Detect closing a connection on a different API than the one that opened it. * Tests for PlacesApi::close_connection * Fix busted benchmarks * Address review feedback * Changelog entry for connection types refactor * Document thread-safety of places API
2019-03-05 23:03:33 +03:00
## Places
2019-03-14 04:03:21 +03:00
### What's New
Refactor places connection management (#718) * This is a proof-of-concept for how we might manage connections. It is currently in a good enough state to see if the idea is worth pursuing. At a minimum, and before landing, we'd: * split the schema.rs changes into its own PR - they aren't strictly needed for what this patch does. * Probably move PlacesAPI into its own source file, and better consider threading considerations - the PlacesAPI instance will end up being called from multiple threads (although the stuff we hand out shouldn't be) * Manage the "sync" connection similarly to how we manage the "write" connection. The PlacesAPI object is probably also where the sync "store" objects can live (as currently we create brand new stores each sync, which isn't as optimized as it should be) * FFI changes needed to support this - this would be a breaking change, but shouldn't be too difficult to manage. * Lots of other cleanup - I figured I'd get comments on the general approach before spending much time cleaning things up. So by all means, offer all suggestions, but the main thing I'd like from this is general approval that we should go ahead with this. * Flesh out the Api more, including the Kotlin side of the fence * First cut at Thom's feedback * Fix nit: IOError => IoError * Return writer connection to API when finished with it, ensure there's only one in kotlin * Avoid duplication of rustCall * Detect closing a connection on a different API than the one that opened it. * Tests for PlacesApi::close_connection * Fix busted benchmarks * Address review feedback * Changelog entry for connection types refactor * Document thread-safety of places API
2019-03-05 23:03:33 +03:00
- A massive rewrite of the Kotlin API has been completed. This distinguishes
reader and writer connections. A brief description of the new types follows.
Note that all the types have corresponding interfaces that allow for them to
be mocked during testing as needed. ([#718](https://github.com/mozilla/application-services/pull/718))
- `PlacesApi`: This is similar to a connection pool, it exists to give out
reader and writer connections via the functions `openReader` and
`getWriter`. The naming distinction is due to there only being a single
writer connection (which is actually opened when the `PlacesApi` is
created). This class generally should be a singleton.
- In addition to `openReader` and `getWriter`, this also includes the
`sync()` method, as that requires a special type of connection.
- `ReadablePlacesConnection`: This is a read-only connection to the places
database, implements all the methods of the API that do not require write
access.
- Specifically, `getVisited`, `matchUrl`, `queryAutocomplete`, `interrupt`,
`getVisitedUrlsInRange`, and `getVisitInfos` all exist on this object.
- `WritablePlacesConnection`: This is a read-write connection, and as such,
contains not only the all reader methods mentioned above, but also the
methods requiring write access, such as:
- `noteObservation`, `wipeLocal`, `runMaintenance`, `pruneDestructively`,
`deleteEverything`, `deletePlace`, `deleteVisitsSince`, `deleteVisitsBetween`,
and `deleteVisit`.
- Note that the semantics of the various methods have not been changed, only
their location.
2019-03-14 04:03:21 +03:00
### Breaking Changes
Refactor places connection management (#718) * This is a proof-of-concept for how we might manage connections. It is currently in a good enough state to see if the idea is worth pursuing. At a minimum, and before landing, we'd: * split the schema.rs changes into its own PR - they aren't strictly needed for what this patch does. * Probably move PlacesAPI into its own source file, and better consider threading considerations - the PlacesAPI instance will end up being called from multiple threads (although the stuff we hand out shouldn't be) * Manage the "sync" connection similarly to how we manage the "write" connection. The PlacesAPI object is probably also where the sync "store" objects can live (as currently we create brand new stores each sync, which isn't as optimized as it should be) * FFI changes needed to support this - this would be a breaking change, but shouldn't be too difficult to manage. * Lots of other cleanup - I figured I'd get comments on the general approach before spending much time cleaning things up. So by all means, offer all suggestions, but the main thing I'd like from this is general approval that we should go ahead with this. * Flesh out the Api more, including the Kotlin side of the fence * First cut at Thom's feedback * Fix nit: IOError => IoError * Return writer connection to API when finished with it, ensure there's only one in kotlin * Avoid duplication of rustCall * Detect closing a connection on a different API than the one that opened it. * Tests for PlacesApi::close_connection * Fix busted benchmarks * Address review feedback * Changelog entry for connection types refactor * Document thread-safety of places API
2019-03-05 23:03:33 +03:00
- Almost the entire API has been rewritten. See "What's New" for
details. ([#718](https://github.com/mozilla/application-services/pull/718))
2019-02-27 23:23:30 +03:00
# 0.18.0 (_2019-02-27_)
[Full Changelog](https://github.com/mozilla/application-services/compare/v0.17.0...v0.18.0)
2019-02-20 00:15:03 +03:00
2019-02-26 01:28:55 +03:00
## FxA
### Breaking Changes
- Swift: `FxAError` has been renamed to `FirefoxAccountError` ([#713](https://github.com/mozilla/application-services/pull/713))
2019-02-20 02:56:00 +03:00
## Places
### What's Fixed
- Autocomplete should no longer return an error when encountering certain emoji ([#691](https://github.com/mozilla/application-services/pull/691))
2019-02-21 02:03:18 +03:00
## Logging
### What's New
- The `rc_log` component now has support for iOS. It is only available as part of the
MozillaAppServices megazord. ([#618](https://github.com/mozilla/application-services/issues/618))
2019-02-20 00:15:03 +03:00
# 0.17.0 (_2019-02-19_)
[Full Changelog](https://github.com/mozilla/application-services/compare/v0.16.1...v0.17.0)
2019-02-08 23:11:00 +03:00
## FxA
### What's New
- We are now using [Protocol Buffers](https://developers.google.com/protocol-buffers/) to pass the Profile data across the FFI boundaries, both on Android and iOS. On Android there should be no breaking changes.
2019-02-15 21:27:35 +03:00
- Kotlin: `Profile` is now a [Data Class](https://kotlinlang.org/docs/reference/data-classes.html).
### Breaking changes
- iOS: You now have to include the `SwiftProtobuf` framework in your projects for FxAClient to work (otherwise you'll get a runtime error when fetching the user profile). It is built into `Carthage/Build/iOS` just like `FxAClient.framework`.
- iOS: In order to build FxAClient from source, you need [swift-protobuf](https://github.com/apple/swift-protobuf) installed. Simply run `brew install swift-protobuf` if you have Homebrew.
- iOS: You need to run `carthage bootstrap` at the root of the repository at least once before building the FxAClient project: this will build the `SwiftProtobuf.framework` file needed by the project.
- iOS: the `Profile` class now inherits from `RustProtobuf`. Nothing should change in practice for you.
2019-02-09 00:19:55 +03:00
## Places
### What's New
- New methods on PlacesConnection (Breaking changes for classes implementing PlacesAPI):
- `fun deleteVisit(url: String, timestamp: Long)`: If a visit exists at the specified timestamp for the specified URL, delete it. This change will be synced if it is the last remaining visit (standard caveat for partial visit deletion). ([#621](https://github.com/mozilla/application-services/issues/621))
- `fun deleteVisitsBetween(start: Long, end: Long)`: Similar to `deleteVisitsSince(start)`, but takes an end date. ([#621](https://github.com/mozilla/application-services/issues/621))
- `fun getVisitInfos(start: Long, end: Long = Long.MAX_VALUE): List<VisitInfo>`: Returns a more detailed set of information about the visits that occured. ([#619](https://github.com/mozilla/application-services/issues/619))
- `VisitInfo` is a new data class that contains a visit's url, title, timestamp, and type.
- `fun wipeLocal()`: Deletes all history entries without recording any sync information. ([#611](https://github.com/mozilla/application-services/issues/611)).
This means that these visits are likely to start slowly trickling back
in over time, and many of them will come back entirely if a full sync
is performed (which may not happen for some time, admittedly). The
intention here is that this is a method that's used if data should be
discarded when disconnecting sync, assuming that it would be desirable
for the data to show up again if sync is reconnected.
For more permanent local deletions, see `deleteEverything`, also added
in this version.
- `fun runMaintenance()`: Perform automatic maintenance. ([#611](https://github.com/mozilla/application-services/issues/611))
This should be called at least once per day, however that is a
recommendation and not a requirement, and nothing dire happens if it is
not called.
The maintenance it may perform potentially includes, but is not limited to:
- Running `VACUUM`.
- Requesting that SQLite optimize our indices.
- Expiring old visits.
- Deleting or fixing corrupt or invalid rows.
- Etc.
However not all of these are currently implemented.
- `fun pruneDestructively()`: Aggressively prune history visits. ([#611](https://github.com/mozilla/application-services/issues/611))
These deletions are not intended to be synced, however due to the way
history sync works, this can still cause data loss.
As a result, this should only be called if a low disk space notification
is received from the OS, and things like the network cache have already
been cleared.
- `fun deleteEverything()`: Delete all history visits. ([#647](https://github.com/mozilla/application-services/issues/647))
For sync users, this will not cause the visits to disappear from the
users remote devices, however it will prevent them from ever showing
up again, even across full syncs, or sync sign-in and sign-out.
See also `wipeLocal`, also added in this version, which is less
permanent with respect to sync data (a full sync is likely to bring
most of it back).
2019-02-09 00:19:55 +03:00
### Breaking Changes
- The new `PlacesConnection` methods listed in the "What's New" all need to be implemented (or stubbed) by any class that implements `PlacesAPI`. (multiple bugs, see "What's New" for specifics).
### What's fixed
- Locally deleted visits deleted using `deleteVisitsSince` should not be resurrected on future syncs. ([#621](https://github.com/mozilla/application-services/issues/621))
2019-02-19 23:37:42 +03:00
- Places now properly updates frecency for origins, and generally supports
origins in a way more in line with how they're implemented on desktop. ([#429](https://github.com/mozilla/application-services/pull/429))
2019-02-09 00:19:55 +03:00
2019-02-08 23:11:00 +03:00
# 0.16.1 (_2019-02-08_)
[Full Changelog](https://github.com/mozilla/application-services/compare/v0.16.0...v0.16.1)
2019-02-01 22:28:48 +03:00
## Logins
### What's Fixed
- iOS `LoginRecord`s will no longer use empty strings for `httpRealm` and `formSubmitUrl` in cases where they claim to use nil. ([#623](https://github.com/mozilla/application-services/issues/623))
- More broadly, all optional strings in LoginRecords were were being represented as empty strings (instead of nil) unintentionally. This is fixed.
- iOS: Errors that were being accidentally swallowed should now be properly reported. ([#640](https://github.com/mozilla/application-services/issues/640))
- Schema initialization/upgrade now happen in a transaction. This should avoid corruption if some unexpected error occurs during the first unlock() call. ([#642](https://github.com/mozilla/application-services/issues/642))
### Breaking changes
- iOS: Code that expects empty strings (and not nil) for optional strings should be updated to check for nil instead. ([#623](https://github.com/mozilla/application-services/issues/623))
2019-02-08 23:11:00 +03:00
- Note that this went out in a non-major release, as it doesn't cause compilation failure, and manually reading all our dependents determined that nobody was relying on this behavior.
2019-02-07 00:34:24 +03:00
## FxA
### What's Fixed
- iOS: Some errors that were being accidentally swallowed should now be properly reported. ([#640](https://github.com/mozilla/application-services/issues/640))
2019-02-07 00:34:24 +03:00
# 0.16.0 (_2019-02-06_)
[Full Changelog](https://github.com/mozilla/application-services/compare/v0.15.0...v0.16.0)
## General
### What's New
2019-02-07 00:34:24 +03:00
- iOS builds now target v11.0. ([#614](https://github.com/mozilla/application-services/pull/614))
- Preparatory infrastructure for megazording iOS builds has landed.([#625](https://github.com/mozilla/application-services/pull/625))
## Places
### Breaking Changes
2019-02-02 00:55:03 +03:00
- Several new methods on PlacesConnection (Breaking changes for classes implementing PlacesAPI):
- `fun interrupt()`. Cancels any calls to `queryAutocomplete` or `matchUrl` that are running on other threads. Those threads will throw an `OperationInterrupted` exception. ([#597](https://github.com/mozilla/application-services/pull/597))
- Note: Using `interrupt()` during the execution of other methods may work, but will have mixed results (it will work if we're currently executing a SQL query, and not if we're running rust code). This limitation may be lifted in the future.
- `fun deletePlace(url: String)`: Deletes all visits associated with the provided URL ([#591](https://github.com/mozilla/application-services/pull/591))
- Note that these deletions are synced!
- `fun deleteVisitsSince(since: Long)`: Deletes all visits between the given unix timestamp (in milliseconds) and the present ([#591](https://github.com/mozilla/application-services/pull/591)).
- Note that these deletions are synced!
2019-02-07 00:34:24 +03:00
### What's New
- Initial support for storing bookmarks has been added, but is not yet exposed over the FFI. ([#525](https://github.com/mozilla/application-services/pull/525))
## FxA
### What's Fixed
- iOS Framework: Members of Avatar struct are now public. ([#615](https://github.com/mozilla/application-services/pull/615))
2019-02-01 22:28:48 +03:00
# 0.15.0 (_2019-02-01_)
[Full Changelog](https://github.com/mozilla/application-services/compare/v0.14.0...v0.15.0)
2019-01-30 22:08:53 +03:00
## General
### What's New
- A new megazord was added, named `fenix-megazord`. It contains the components for FxA and Places (and logging). ([#585](https://github.com/mozilla/application-services/issues/585))
- Note: To use this, you must be on version 0.3.1 of the gradle plugin.
## Logins
### What's Fixed
- Fix an issue where unexpected errors would become panics. ([#593](https://github.com/mozilla/application-services/pull/593))
- Fix an issue where syncing with invalid credentials would be reported as the wrong kind of error (and cause a panic because of the previous issue). ([#593](https://github.com/mozilla/application-services/pull/593))
## Places
2019-02-01 03:11:36 +03:00
### What's New
- New method on PlacesConnection (breaking change for classes implementing PlacesAPI): `fun matchUrl(query: String): String?`. This is similar to `queryAutocomplete`, but only searches for URL and Origin matches, and only returns (a portion of) the matching url (if found), or null (if not). ([#595](https://github.com/mozilla/application-services/pull/595))
### What's Fixed
- Autocomplete will no longer return an error when asked to match a unicode string. ([#298](https://github.com/mozilla/application-services/issues/298))
- Autocomplete is now much faster for non-matching queries and queries that look like URLs. ([#589](https://github.com/mozilla/application-services/issues/589))
2019-01-24 22:48:41 +03:00
## FxA
### What's New
- It is now possible to know whether a profile avatar has been set by the user. ([#579](https://github.com/mozilla/application-services/pull/579))
### Breaking Changes
- The `avatar` accessor from the `Profile` class in the Swift framework now returns an optional `Avatar` struct instead of a `String`. ([#579](https://github.com/mozilla/application-services/pull/579))
# 0.14.0 (_2019-01-23_)
[Full Changelog](https://github.com/mozilla/application-services/compare/v0.13.3...v0.14.0)
2019-01-12 00:09:22 +03:00
2019-01-19 01:47:44 +03:00
## General
### What's New
- A new component was added for customizing how our Rust logging is handled. It allows Android code to get a callback whenever a log is emitted from Rust (Most users will not need to use this directly, but instead will consume it via the forthcoming helper that hooks it directly into android-components Log system in [android-components PR #1765](https://github.com/mozilla-mobile/android-components/pull/1765)). ([#472](https://github.com/mozilla/application-services/pull/472))
- The gradle megazord plugin updated to version 0.3.0, in support of the logging library. Please update when you update your version of android-components. ([#472](https://github.com/mozilla/application-services/pull/472))
2019-01-19 01:47:44 +03:00
- In most cases, opaque integer handles are now used to pass data over the FFI ([#567](https://github.com/mozilla/application-services/issues/567)). This should be more robust, and allow detection of many types of errors that would previously cause silent memory corruption.
This should be mostly transparent, but is a semi-breaking semantic change in the case that something throws an exception indicating that the Rust code paniced (which should only occur due to bugs anyway). If this occurs, all subsequent operations on that object (except `close`/`lock`) will cause errors. It is "poisoned", in Rust terminology. (In the future, this may be handled automatically)
2019-01-19 01:47:44 +03:00
This may seem inconvenient, but it should be an improvement over the previous version, where we instead would simply carry on despite potentially having corrupted internal state.
- Build settings were changed to reduce binary size of Android `.so` by around 200kB (per library). ([#567](https://github.com/mozilla/application-services/issues/567))
- Rust was updated to 1.32.0, which means we no longer use jemalloc as our allocator. This should reduce binary size some, but at the cost of some performance. (No bug as this happens automatically as part of CI, see the rust-lang [release notes](https://blog.rust-lang.org/2019/01/17/Rust-1.32.0.html#jemalloc-is-removed-by-default) for more details).
### Breaking Changes
- Megazord builds will no longer log anything by default. Logging must be enabled as described "What's New". ([#472](https://github.com/mozilla/application-services/pull/472))
## Places
### What's Fixed
- PlacesConnection.getVisited will now return that invalid URLs have not been visited, instead of throwing. ([#552](https://github.com/mozilla/application-services/issues/552))
- PlacesConnection.noteObservation will correctly identify url parse failures as such. ([#571](https://github.com/mozilla/application-services/issues/571))
- PlacesConnections not utilizing encryption will not make calls to mlock/munlock on every allocation/free. This improves performance up to 6x on some machines. ([#563](https://github.com/mozilla/application-services/pull/563))
- PlacesConnections now use WAL mode. ([#555](https://github.com/mozilla/application-services/pull/563))
## FxA
### Breaking Changes
Some APIs which are semantically internal (but exposed for various reasons) have changed.
- Android: Some `protected` methods on `org.mozilla.fxaclient.internal.RustObject` have been changed (`destroy` now takes a `Long`, as it is an opaque integer handle). This object should not be considered part of the public API of FxA, but it is still available. Users using it are recommended not to do so. ([#567](https://github.com/mozilla/application-services/issues/567))
- iOS: The type `RustOpaquePointer` was replaced by `RustHandle`, which is a `RustPointer<UInt64>`. While these are technically part of the public API, they may be removed in the future and users are discouraged from using them. ([#567](https://github.com/mozilla/application-services/issues/567))
2019-01-12 00:09:22 +03:00
# 0.13.3 (_2019-01-11_)
[Full Changelog](https://github.com/mozilla/application-services/compare/v0.13.2...v0.13.3)
## Places
### What's Fixed
- Places will no longer log PII. ([#540](https://github.com/mozilla/application-services/pull/540))
2019-01-11 22:29:49 +03:00
# 0.13.2 (_2019-01-11_)
[Full Changelog](https://github.com/mozilla/application-services/compare/v0.13.1...v0.13.2)
## Firefox Accounts
### What's New
- The fxa-client android library will now write logs to logcat. ([#533](https://github.com/mozilla/application-services/pull/533))
2019-01-11 22:29:49 +03:00
- The fxa-client Android and iOS librairies will throw a differentiated exception for general network errors. ([#535](https://github.com/mozilla/application-services/pull/535))
2019-01-10 05:10:40 +03:00
# 0.13.1 (_2019-01-10_)
[Full Changelog](https://github.com/mozilla/application-services/compare/v0.13.0...v0.13.1)
Note: This is a patch release that works around a bug introduced by a dependency. No functionality has been changed.
## General
### What's New
N/A
### What's Fixed
- Network requests on Android. Due to a [bug in `reqwest`](https://github.com/seanmonstar/reqwest/issues/427), it's version has been pinned until we can resolve this issue. ([#530](https://github.com/mozilla/application-services/pull/530))
# 0.13.0 (_2019-01-09_)
[Full Changelog](https://github.com/mozilla/application-services/compare/v0.12.1...v0.13.0)
## General
### What's New
- Upgraded openssl to 1.1.1a ([#474](https://github.com/mozilla/application-services/pull/474))
### What's Fixed
2019-01-09 21:16:40 +03:00
- Fixed issue where backtraces were still enabled, causing crashes on some android devices ([#509](https://github.com/mozilla/application-services/pull/509))
- Fixed some panics that may occur in corrupt databases or unexpected data. ([#488](https://github.com/mozilla/application-services/pull/488))
## Places
### What's New
N/A
### What's fixed
2019-01-09 21:16:40 +03:00
- Autocomplete no longer returns more results than requested ([#489](https://github.com/mozilla/application-services/pull/489))
## Logins
### Deprecated or Breaking Changes
2019-01-09 21:16:40 +03:00
- Deprecated the `reset` method, which does not perform any useful action (it clears sync metadata, such as last sync timestamps and the mirror table). Instead, use the new `wipeLocal` method, or delete the database file. ([#497](https://github.com/mozilla/application-services/pull/497))
### What's New
2019-01-09 21:16:40 +03:00
- Added the `wipeLocal` method for deleting all local state while leaving remote state untouched. ([#497](https://github.com/mozilla/application-services/pull/497))
- Added `ensureLocked` / `ensureUnlocked` methods which are identical to `lock`/`unlock`, except that they do not throw if the state change would be a no-op (e.g. they do not require that you check `isLocked` first). ([#495](https://github.com/mozilla/application-services/pull/495))
- Added an overload to `unlock` and `ensureUnlocked` that takes the key as a ByteArray. Note that this is identical to hex-encoding (with lower-case hex characters) the byte array prior to providing it to the string overload. ([#499](https://github.com/mozilla/application-services/issues/499))
### What's Fixed
2019-01-09 21:16:40 +03:00
- Clarified which exceptions are thrown in documentation in cases where it was unclear. ([#495](https://github.com/mozilla/application-services/pull/495))
- Added `@Throws` annotations to all methods which can throw. ([#495](https://github.com/mozilla/application-services/pull/495))