chromium/src
0
Fork 0
Code Activity

android_isolated_splits.md: Mention our compile check for invalid package-private access

Browse Source 
Change-Id: Ifd279005da59b04ed685aae968ecb9ddcaefec44
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6317630
Auto-Submit: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Andrew Grieve <agrieve@chromium.org>
Reviewed-by: Mohamed Heikal <mheikal@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1427332}
This commit is contained in:
Andrew Grieve
2025-03-03 12:58:20 -08:00
committed by Chromium LUCI CQ
parent 5003ed5a6c
commit 638a46aba3
1 changed files with 3 additions and 2 deletions

5
docs/android_isolated_splits.md

@ -334,10 +334,11 @@ Having Android Framework call `Bundle.setClassLoader()` is tracked in
[a custom ClassLoader]: https://source.chromium.org/search?q=symbol:ChromeBaseAppCompatActivity.getClassLoader&ss=chromium
[b/260574161]: https://issuetracker.google.com/260574161
### Calling Methods Across a Split Boundary
### Package Private Methods
Due to having different ClassLoaders, package-private methods don't work across
the boundary, even though they will compile.
the boundary, even though they will compile. Release builds will fail during
the R8 step, which has a check for cross-split package-private access.
**Work around:**