Do we really need to block this on checking in the sources? WebView is blocked upstreaming the N java code on this, which means right now nobody can build a current version webview properly from the open source repo :(
We've got the sources checked in for the SDK, and I'd be uncomfortable checking in the N SDK alongside the M SDK sources. I don't know if we've asked the open source folks about this specifically, though.
We're still urgently awaiting this to upstream the WebView N changes. External users are now querying why they can't build an N webview :/
Not blaming anyone for the delay here because there was legitimate confusion about whether we needed to wait for the AOSP source release or not, but we've now missed upstreaming the WebView code for M51, M52, M53 and M54. :(
For future rolls, we need to make this a priority that happens as soon as the public SDK is available - waiting for the AOSP source release is definitely much too late.
I'm setting this as an M55 beta blocker to get it on people's dashboards, but it needs to be done several weeks before the M55 branch point to give us time to actually upstream the webview changes that depend on it.
Is there an ETA for this work? It seems like several folks are waiting for it and it would be great to have an idea of when we can start building against it for planning purposes.
Sorry for the delays here, I'm working through a lint issue and things were delayed last week due to some production outages. My ETA is by the end of the week.
We've landed the SDK in android_tools, and verified that with lint errors suppressed we get a functional binary. Progressing on the CL with the lint errors correctly suppressed.
It's great to see the progress on this bug but I was wondering if the plan is to merge the remainder of the changes (I'm not sure how much work is left) into the M55 release branch or if teams dependent on these changes will need to work out of M56 for their N specific functionality and features.
Since we're actually close to the M55 beta release point, having this here is polluting the critical path queue, so I'm going to move it to stable. Based on some of torne's earlier assertion this should have been fixed a few weeks ago, so hopefully we can make this happen soon? Glad to see all the recent activity, do we have any ETA?
Thanks for the work everyone (especially stip@) has put in to try to get this rolled.
Once it actually lands and sticks, I think it'd be useful to look at why this was so difficult/time-consuming (past the original issue of waiting for the source when we didn't really need to), and try to figure out if there's anything we can do to make it easier/quicker next time.
WebView's process around new android releases really depends on being able to roll the public SDK in chromium quickly, ideally at least a week before the very next branch point - for the N SDK it would have been ideal to land the roll by mid-august so that we had time to upstream the WebView N code for the M54 branch point, and currently it looks like we're barely going to make M56.
Are there plans to update 'default_lint_android_sdk_version' from API level 23 to 24? I see some lint errors when using new N functionality which are resolved when the lint target is updated.
