Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

Closes #270: Integrate browser-storage-sync #294

Merged
merged 1 commit into from
Jan 29, 2019

Conversation

grigoryk
Copy link
Contributor

This adds support for persisting history and providing toolbar url autocomplete suggestions via browser-storage-sync component.

Underneath, this is powered by a Rust version of places.

You can poke at the sqlite database this creates over at /data/data/org.mozilla.fenix.debug/files/places.sqlite.

Once we integrate FxA, feature-sync and upcoming SyncManager components, this component will also power history sync.

@ghost ghost assigned grigoryk Jan 29, 2019
@ghost ghost added in progress labels Jan 29, 2019
@colintheshots colintheshots merged commit 0e39656 into mozilla-mobile:master Jan 29, 2019
@ghost ghost removed in progress labels Jan 29, 2019
@grigoryk grigoryk deleted the browserSyncStorage branch January 29, 2019 21:34
grigoryk pushed a commit to grigoryk/fenix that referenced this pull request Jan 30, 2019
…ted architectures

This fixes a regression from mozilla-mobile#294

That patch adds a dependency which loads some native libraries. Those native libs are
shipped for a variety of architectures. Specifically, there are versions of aarch64 and armv7.
What seems to happen is that since those libraries are loaded first (GV is lazily initialized
after history stuff), and since aarch64 versions of these libs is chosen by the native loader,
consequent native loads select for the same abi type. aarch64 version of libmozglue isn't there,
loader fails to find it and we crash.

Being explicit with the abiFilter in the product flavour definitions strips out aarch64 app-services
libs from the apk. When they're loaded first, armv7 versions are picked (since we don't have any other
ones), and everything works correctly afterwards.

Another way to achieve the same result would be to exclude arm64 libs via packagignOptions directive:
packagingOptions { exclude "lib/arm64-v8a/**" }

... but that's a less flexible approach in the longer term.
boek pushed a commit that referenced this pull request Jan 30, 2019
…ted architectures

This fixes a regression from #294

That patch adds a dependency which loads some native libraries. Those native libs are
shipped for a variety of architectures. Specifically, there are versions of aarch64 and armv7.
What seems to happen is that since those libraries are loaded first (GV is lazily initialized
after history stuff), and since aarch64 versions of these libs is chosen by the native loader,
consequent native loads select for the same abi type. aarch64 version of libmozglue isn't there,
loader fails to find it and we crash.

Being explicit with the abiFilter in the product flavour definitions strips out aarch64 app-services
libs from the apk. When they're loaded first, armv7 versions are picked (since we don't have any other
ones), and everything works correctly afterwards.

Another way to achieve the same result would be to exclude arm64 libs via packagignOptions directive:
packagingOptions { exclude "lib/arm64-v8a/**" }

... but that's a less flexible approach in the longer term.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants