It would be good if we can roll Android SDK to N-MR1 for upstream. I think it should have been released to AOSP by now.
My need is not super urgent, though. Need to check for build version code > N_MR1 for some cases, but I can hardcode the number. Filing this for tracking purposes.
I'm trying to clean up some of the reflection and special includes we added for NMR1 and the trybots are failing to compile. It's throwing errors related to not finding the new XML attributes added for launcher shortcuts in NMR1.
When I compile regular chrome locally everything works fine, but monochrome fails to compile. Is it possible monorail is still using the N sdk?
Additionally, the proguard step the trybot failed on was...
android_webview:system_webview_apk__proguard
Between that failing, and you saying you had trouble compiling Monochrome, this is probably some webview related build issue. Probably something I missed updating.
@Boliu, Im not too familiar with it, does the...
third_party/android_platform/webview/frameworks_7.0.0_r1.jar
...JAR have to be updated when we roll the upstream SDK?
Not having the N MR1 version of this jar is what I suspect is causing the build issues for twellington@
Comment 1 by jbudorick@chromium.org
, Feb 3 2017