Status Update
No update yet.
Comments
yb...@google.com
ap...@google.com
The location of where this is being placed in the app bundle by AGP (as quoted in
) is also incorrect - rather than BUNDLE_METADATA/assets/dexopt/baseline.prof it should be at BUNDLE_METADATA/com.android.tools.build.profiles/baseline.prof or similar, to correctly identify what kind of metadata this is within the bundle. So that baseline profiles generated from android studio via the android app bundle actually work, we'd need to make these changes in AGP for the next stable release of studio. b/226434396#comment1
Currently the baseline profile ends up in BUNDLE_METADATA/assets/dexopt/baseline.prof{m}.
It needs to end up in BUNDLE_METADATA/com.android.tools.build.profiles/baseline.prof{m} or something so we can disambiguate between the types of metadata.
da...@google.com
Related public bug:
Description
Version used: 2.1
Devices/Android versions reproduced on: Google Pixel 3 XL | Android 9.0
c/o (Daniel Santiago Rivera <danysantiago@google.com>)
Room now supports FTS3/4 as well as built in SQLite3 tokenizers. We desire the ability to utilize our own custom tokenizers packaged in with our own sqlite custom implementations.
Perhaps adding a parameter to the @Fts4 annotation (customTokenizer = foo) and pass in any related arguments to the tokenizer as well.