Updating to 26.1 will be tricky as we can't use the SDK manager and there are new dependencies (arch components) that trigger new issues. Planning to step it up to 25.1.0 for now, which is already in the repo. That release already contains bugfixes
Updates, since I'll be off for 2 weeks.
I gave a shot to the 2 updates and ran into various issues:
- 25.1.0: builds fine, send a CL already (https://chromium-review.googlesource.com/c/chromium/src/+/690003) but it seems to affect UIs. Would need to check quickly that everything is all right and that the triggering of render test is not reflecting a UX issue. Additionally it introduces a bug (related to media router, freezes device and requires reboot) only fixed in 25.2. Not too keen on rolling to fix a bug if we introduce a potentially worse one.
- 26.1.0: added a script to download it, but there seems to be backwards incompatible changes:
+ style removed: TextAppearance.StatusBar.EventContent.* => I don't see mentions of the change but we can't reference it anymore. awdf@, any thoughts on this? It affects Web notifications
+ AsyncInitializationActivity depends on LifecycleOwner from the Architecture components now, so that additional dependency needs to be added in a bunch of places.
CLs:
+ New binaries: https://chromium-review.googlesource.com/#/c/android_tools/+/692895
+ Chromium changes: https://chromium-review.googlesource.com/#/c/chromium/src/+/692894
We build release builds with the 26.0.0 version of the support library. We could roll downstream. Or, ideally, pull in the new support library in our upstream android-26 directory.
Haah, thank you for your hard work, Nicolas! Scripting this is already paying off. :D
Hopefully with the new android_tools sdk refactor this will all be easier in the future.
Comment 1 by dgn@chromium.org
, Sep 28 2017