Add an activity that allows whitelisted applications to clear all data in Chrome.

chrome/android/java_staging/AndroidManifest.xml

 <?xml version="1.0" encoding="utf-8"?>
 <!-- Copyright 2015 The Chromium Authors. All rights reserved.
      Use of this source code is governed by a BSD-style license that can be
      found in the LICENSE file. -->
 
 <!--
 Note: This is a jinja2 template, processed at build time into the final manifest.
 
 Blocks denoted with { % block some_name % }foo{ % endblock % } can be overridden
 by a child template that "extends" this file.
@@ skipping 332 matching lines @@
         <activity android:name="org.chromium.chrome.browser.media.remote.ExpandedControllerActivity"
             android:theme="@style/MainTheme"
             android:label="Chrome.ExpandedControllerActivity"
             android:hardwareAccelerated="true"
             android:launchMode="singleTask"
             android:noHistory="true"
             android:configChanges="orientation|keyboardHidden|keyboard|screenSize|mcc|mnc"
             android:excludeFromRecents="true">
         </activity>
 
+        <activity android:name="org.chromium.chrome.browser.childaccounts.ResetDataActivity"
+            android:theme="@android:style/Theme.Translucent.NoTitleBar"

[palmer, 2015/06/17 21:55:17]

As declared, any other package on the device could invoke this Activity. Is that
safe/a good idea/intended?

There is a nice, declarative way to ensure that only the system or Chrome can
invoke the Activity: declare a signatureOrSystem Permission, and then require
that callers of this Activity must have it. Thus, only Chrome (or possibly other
Google packages) or the Android platform could launch the Activity.

http://developer.android.com/guide/topics/manifest/activity-element.html#prmsn

http://developer.android.com/guide/topics/manifest/permission-element.html

[Bernhard Bauer, 2015/06/18 09:08:53]

The problem with declaring a permission is that the permission has to be known
to the system before it can be granted to the app, which means that now Chrome
has to be installed before the app that calls this, which might not be the case.

Also, I think signatureOrSystem wouldn't work here, because the calling app is
signed with a different (but still first-party) key than Chrome is. At that
point, we'd have to whitelist a specific key... which is almost the same as I'm
doing here anyway :)

+            android:exported="true"
+            android:excludeFromRecents="true">
+        </activity>
+
         <activity android:name="org.chromium.chrome.browser.document.CipherKeyActivity"
             android:launchMode="singleInstance"
             android:theme="@android:style/Theme.Translucent.NoTitleBar"
             android:excludeFromRecents="true">
         </activity>
 
         <!-- Providers for chrome data. -->
         <provider android:name="org.chromium.chrome.browser.ChromeBrowserProviderStaging"
             android:authorities="{{ manifest_package }}.ChromeBrowserProvider;{{ manifest_package }}.browser;{{ manifest_package }}"
             android:exported="true">
@@ skipping 220 matching lines @@
 
         <meta-data android:name="org.chromium.content.browser.SMART_CLIP_PROVIDER"
             android:value="org.chromium.content.browser.SmartClipProvider"/>
         <meta-data android:name="org.chromium.components.service_tab_launcher.SERVICE_TAB_LAUNCHER"
                    android:value="org.chromium.chrome.browser.ChromeServiceTabLauncher" />
 
         {% block extra_application_definitions %}
         {% endblock %}
     </application>
 </manifest>