Fixes for moving chrome to isolated split
This patch has a few fixes needed before enabling isolated splits in canary: - Make module_installer load classes from the application context ClassLoader instead of using Class.forName, since that may be using the base ClassLoader and not have the chrome split classes - Fix some of the bundle smoke tests since the DFMs are merged into the chrome DFM. - Fix the chrome resources package (org.chromium.chrome.R) clashing with the base module's resources when the APK package name matches. - Ignore chime services which are not defined in the base module, since they will not be used with isolated splits. Bug: 1126301 Change-Id: Ib149894636863408c5fd37054eacb48c214b5b3f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2472707Reviewed-by:Andrew Grieve <agrieve@chromium.org> Commit-Queue: Clark DuVall <cduvall@chromium.org> Cr-Commit-Position: refs/heads/master@{#818724}
Showing
Please register or sign in to comment