Because of the way we will make calls between the WebView Support Library, and the WebView Glue layer (essentially through class+methodname lookups), if we rename the package, or any of the classes in the interfaces for communication between the support library, and the webview glue layer, we will break that communication in older WebView versions.
Should we have some mechanism to allow for package name changes? (like sending the package name of the support library interfaces to the webview apk on initialization).
Relying on not making changes to an interface like this (ever) seems brittle, I wonder if I'm missing something even more restricting (that the package name) that we can't change after creating the dependency between the support library and the webview apk..
Comment 1 by gsennton@chromium.org
, Dec 18 2017