Chromium Code Reviews Chromium Code Reviews
Issue 2527953002:
[gmscore] Add Google Play services documentation (Closed)
| OLD | NEW |
|---|---|
| (Empty) | |
| 1 # Google Play services in Chrome for Android | |
| 2 | |
| 3 [TOC] | |
| 4 | |
| 5 Google employee? See [go/chrome-gms](https://goto.google.com/chrome-gms) for | |
| 6 more info. | |
| 7 | |
| 8 ## General setup | |
| 9 | |
| 10 The Google Play services are a combination of [services][play_store] exposed on | |
| 11 Android devices, and [libraries][dev_doc] to interact with them. Chrome relies | |
|
jbudorick
2016/12/06 18:23:49
nit: no , after devices
| |
| 12 on them for critical features like Sign in, Feedback or Cast. | |
| 13 | |
| 14 The standard way of adding the Google Play services as a dependency to a project | |
| 15 is to import it through the Android SDK manager, as a Maven repository. That | |
|
jbudorick
2016/12/06 18:23:49
nit: no , after manager
| |
| 16 repository contains multiple versions of the library, split into separate APIs | |
|
jbudorick
2016/12/06 18:23:49
nit: no , after library
| |
| 17 (for example Cast, GCM, Android Pay, etc). To avoid downloading a lot of data we | |
| 18 won't need to build Chrome, android checkouts of Chromium will download an | |
|
jbudorick
2016/12/06 18:23:49
nit: Use present rather than future tense here. s/
| |
| 19 archive containing only the APIs we currently need in Chrome, and in a single | |
| 20 version. | |
| 21 | |
| 22 The up to date list of clients and version used can be seen in | |
| 23 [//build/android/play_services/config.json][config_json_rel_path]. | |
| 24 | |
| 25 **Note**: If you are working on a feature that requires different or more recent | |
| 26 APIs, you will need to locally download the Google Play services SDK repository. | |
| 27 | |
| 28 The simplest way to download the latest SDK is to run: | |
| 29 | |
| 30 ``` | |
| 31 $CHROMIUM_SRC/build/android/play_services/update.py sdk | |
| 32 ``` | |
| 33 | |
| 34 Check out the help of that script for more info. | |
| 35 | |
| 36 [play_store]: https://play.google.com/store/apps/details?id=com.google.android.g ms | |
| 37 [dev_doc]: https://developers.google.com/android/guides/overview | |
| 38 [config_json_rel_path]: ../build/android/play_services/config.json | |
| 39 | |
| 40 ## Adding a dependency on new APIs | |
| 41 | |
| 42 As explained above, the default checkout has access to only a specific set of | |
| 43 APIs during builds. If your CL depends on some APIs that are not included in the | |
| 44 build, you will need [file an issue][bug_link] to request an update of our | |
| 45 dependencies. | |
| 46 | |
| 47 Not doing so could make the CL fail on the trybots and commit queue. Even if it | |
| 48 passes, it might fail on the internal bots, and result in the CL getting | |
|
jbudorick
2016/12/06 18:23:49
nit: no , after bots
| |
| 49 reverted. So please make sure the APIs are available to the bots before | |
|
jbudorick
2016/12/06 18:23:48
nit: s/. So/, so/
| |
| 50 submitting. | |
| 51 | |
| 52 [bug_link]:https://bugs.chromium.org/p/chromium/issues/entry?labels=Restrict-Vie w-Google,pri-1,Hotlist-GooglePlayServices&owner=dgn@chromium.org&os=Android | |
| OLD | NEW |
