#3: hrm, good question. I think the circumstances under which that occurred would still occur today due to our continued reliance on public_android_sdk.
ctzsm@ I'm hitting an issue related to ClassRegister. Is my checkout misconfigured, or do others have the same bug?
$ # try to build any of "chrome_apk", "chrome_modern_apk", or "monochrome_apk"
...
Warning: org.chromium.chrome.browser.ClassRegister: can't find referenced class org.chromium.chrome.browser.ClassRegisterImpl
Warning: org.chromium.chrome.browser.ClassRegister: can't find referenced class org.chromium.chrome.browser.ClassRegisterImpl
Warning: org.chromium.chrome.browser.ClassRegister: can't find referenced class org.chromium.chrome.browser.ClassRegisterImpl
Warning: there were 3 unresolved references to classes or interfaces.
ntfschr@, yeah we hit that proguard warning yesterday, it should be fine now. CL in #c21 resolve this issue, it wasn't propagated to downstream until last night. Sorry for the inconvenience.
jbudorick@, will platform-tools be upgraded to 28 too? We just noticed on our end that some tools get confused by the versions being out of sync (namely, in a gradle-based build some linters silently don't run)
Comment 1 by wnwen@chromium.org
, Jun 14 2018