Update Google Play services to v5 (9.4) |
|||||||||||||||||||
Issue descriptionThat version has been released recently: https://developers.google.com/android/guides/releases Problem: The monolithic JAR does not ship anymore through Android SDK Manager, so we have to update the build to work with the new binaries. ⛆ |
|
|
,
Jun 29 2016
,
Jul 20 2016
It looks like AAR support is in place. Can play services be updated now?
,
Jul 28 2016
,
Aug 2 2016
,
Aug 2 2016
Rolling internal now but apparently I don't have access to roll public.
,
Aug 3 2016
I gave it a better look today, so: - We still have a monolithic AAR, so not too many changes to be made - I was afraid of conflicts with the support library AARs, the library is under extras/android/m2repo and gms under extras/google/m2repo, so it's fine! - I should be able to send the updated script for review this week.
,
Aug 3 2016
(for the public update)
,
Aug 3 2016
The following revision refers to this bug: https://chrome-internal.googlesource.com/clank/internal/apps/+/70a1fdaba2b4598f5fce58ab37b1cf3c427913e4 commit 70a1fdaba2b4598f5fce58ab37b1cf3c427913e4 Author: Paul Miller <paulmiller@google.com> Date: Tue Aug 02 19:32:32 2016
,
Aug 3 2016
back to dgn@ for public update
,
Aug 10 2016
,
Aug 11 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/71d53fa016887abec5807c7dfcd9e93ec0ab12a5 commit 71d53fa016887abec5807c7dfcd9e93ec0ab12a5 Author: agrieve <agrieve@chromium.org> Date: Thu Aug 11 16:44:44 2016 Pass input_jars_paths of libs to final proguard step This comes up when a library / prebuilt has a dependency on apache http, such as is the case with some play services libraries. If pre-proguarding is turned off, the final apk proguard() step fails without this change. BUG= 624324 Review-Url: https://codereview.chromium.org/2227523002 Cr-Commit-Position: refs/heads/master@{#411358} [modify] https://crrev.com/71d53fa016887abec5807c7dfcd9e93ec0ab12a5/build/android/gyp/write_build_config.py [modify] https://crrev.com/71d53fa016887abec5807c7dfcd9e93ec0ab12a5/build/config/android/internal_rules.gni [modify] https://crrev.com/71d53fa016887abec5807c7dfcd9e93ec0ab12a5/build/config/android/rules.gni
,
Aug 19 2016
,
Aug 22 2016
The pending CL to update the library dependency is https://codereview.chromium.org/2209233002/ On hold until the downstream issues are fixed: see issue 639494 and b/30869015
,
Aug 22 2016
,
Aug 22 2016
Why is that blocking? You can still roll trunk while I'm reverting m53.
,
Aug 22 2016
I am not sure we should be rolling to v5 without agreement on what to do about the memory regression in M54 with the new GMS core.
,
Aug 22 2016
Exactly, I'd prefer to have downstream always moving forward first, as building with a newer SDK is not an issue there. If we move upstream and start using new APIs, downstream builds would break and upstream developers would not be aware of it. And in general, we want to have the same version on both sides.
,
Sep 1 2016
,
Sep 1 2016
,
Sep 4 2016
,
Sep 4 2016
,
Sep 6 2016
,
Sep 6 2016
,
Oct 28 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/220f57b3c7299133c089ce3c4ede7861cb8bb1e8 commit 220f57b3c7299133c089ce3c4ede7861cb8bb1e8 Author: dgn <dgn@chromium.org> Date: Fri Oct 28 11:22:06 2016 [gmscore] Update the Play services to 9.8 and load from AARs - Update the build to load the play services library from split AARs. - Update the upload/download script to handle the new library distribution format - Roll the dependencies to 9.8 BUG= 624324 ,659366 Review-Url: https://codereview.chromium.org/2209233002 Cr-Commit-Position: refs/heads/master@{#428333} [modify] https://crrev.com/220f57b3c7299133c089ce3c4ede7861cb8bb1e8/build/android/play_services/LICENSE.sha1 [modify] https://crrev.com/220f57b3c7299133c089ce3c4ede7861cb8bb1e8/build/android/play_services/config.json [modify] https://crrev.com/220f57b3c7299133c089ce3c4ede7861cb8bb1e8/build/android/play_services/google_play_services_library.zip.sha1 [modify] https://crrev.com/220f57b3c7299133c089ce3c4ede7861cb8bb1e8/build/android/play_services/update.py [modify] https://crrev.com/220f57b3c7299133c089ce3c4ede7861cb8bb1e8/build/android/play_services/update_test.py [modify] https://crrev.com/220f57b3c7299133c089ce3c4ede7861cb8bb1e8/build/secondary/third_party/android_tools/BUILD.gn [modify] https://crrev.com/220f57b3c7299133c089ce3c4ede7861cb8bb1e8/chrome/android/java/proguard.flags
,
Oct 28 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/0ea787ad5d60a2bc91e15333d136da238b7ebf55 commit 0ea787ad5d60a2bc91e15333d136da238b7ebf55 Author: dgn <dgn@chromium.org> Date: Fri Oct 28 17:06:00 2016 Define separate variable for the sdk root used to load gmscore. BUG= 624324 TBR=agrieve@chromium.org Review-Url: https://codereview.chromium.org/2458083002 Cr-Commit-Position: refs/heads/master@{#428398} [modify] https://crrev.com/0ea787ad5d60a2bc91e15333d136da238b7ebf55/build/config/android/config.gni [modify] https://crrev.com/0ea787ad5d60a2bc91e15333d136da238b7ebf55/build/secondary/third_party/android_tools/BUILD.gn
,
Oct 31 2016
|
||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by dgn@chromium.org
, Jun 29 2016