| commit | f7f1f6483ca71bd81ae4fafe83e82bc1f4c89022 | [log] [tgz] |
|---|---|---|
| author | Pavel Shmakov <pshmakov@google.com> | Fri Apr 12 13:32:08 2019 |
| committer | Commit Bot <commit-bot@chromium.org> | Fri Apr 12 13:33:44 2019 |
| tree | 2681d1d60e0bd0e1f3bb9292d7978cd0c2d7883d | |
| parent | b0d6c6e86d8046fa62135cebb7bc59d9feac9f89 [diff] |
Don't start a new TWA when service connection is restored If Chrome gets killed in background, but client app doesn't, then upon user's return to TWA, Chrome restarts, and the framework automatically re-establishes the service connection. That leads to the client launching another instance of TWA. This CL fixes that. Change-Id: I88266b24d820d6e294276536d3488f556c43d967 Reviewed-on: https://chromium-review.googlesource.com/c/custom-tabs-client/+/1564746 Commit-Queue: Pavel Shmakov <pshmakov@chromium.org> Reviewed-by: Peter Conn <peconn@chromium.org>
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.
Using Custom Tabs should be easy. This repository hosts examples and in-depth documentation. The examples are importable as projects into the Android Studio.
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.
We accept contributions to Custom Tabs examples and documentation. Please see our contributor's guide.