Injecting package name to CCT support lib AndroidManifest and merge it into imported apps

This CL tries to achieve injecting package name variable into the
provider in the AndroidManifest of CCT support lib. The AndroidManifest
has a provider whose authorities should be inflated different package
names based on the imported apps.

This is achieved by having a build variable ${package_name} in the
AndroidManifest of CCT support lib. When imported, the AndroidManifest
is merged into app's AndroidManifest and inflate with the app's package
name.

Bug: 775798
Change-Id: I9cb804a972abd5e80e853ca1a1ac7bba4627ec61
Reviewed-on: https://chromium-review.googlesource.com/874912
Commit-Queue: Lei Tian <ltian@chromium.org>
Reviewed-by: Yusuf Ozuysal <yusufo@chromium.org>
3 files changed
tree: 272bb35da191fb0e9335bb9fb5e92377cd35d3e3
  1. Application/
  2. customtabs/
  3. demos/
  4. gradle/
  5. infra/
  6. shared/
  7. svgomg/
  8. .gitignore
  9. build.gradle
  10. codereview.settings
  11. CONTRIBUTING.md
  12. CREDITS
  13. gradlew
  14. gradlew.bat
  15. LICENSE
  16. OWNERS
  17. README.md
  18. settings.gradle
  19. Using.md
README.md

Chrome Custom Tabs - Examples and Documentation

Chrome Custom Tabs provides a way for an application to customize and interact with a Chrome Activity on Android. This makes the web content feel like being a part of the application, while retaining the full functionality and performance of a complete web browser.

Examples

Using Custom Tabs should be easy. This repository hosts examples and in-depth documentation. The examples are importable as projects into the Android Studio.

Bugs, Issues and Discussion

We want to hear your feedback! Please create bugs and start discussions using this template. Please use the template for any issues related to the Custom Tabs APIs, their implementation in Chrome, the examples in this repository, and related functionality of the Android Support Library.

Note: we know that the GitHub issue tracker is great! However, since Custom Tabs is mostly driven by Chrome developers, and we want to keep all bugs in one place, we prefer the Chromium issue tracker at the moment.

Contributing

We accept contributions to Custom Tabs examples and documentation. Please see our contributor's guide.