Upstream: Launch WebApkActivity from WebAPK.

chrome/android/java/AndroidManifest.xml

Index: chrome/android/java/AndroidManifest.xml
diff --git a/chrome/android/java/AndroidManifest.xml b/chrome/android/java/AndroidManifest.xml
index 858b3f3da8dc2df40f1ff8bec89a900d40868958..06c406030298b9758adb53c5a4df37df3f154f40 100644
--- a/chrome/android/java/AndroidManifest.xml
+++ b/chrome/android/java/AndroidManifest.xml
@@ -410,6 +410,41 @@ by a child template that "extends" this file.
             android:label="@string/webapp_activity_title">
         </activity-alias>
         {% endfor %}
+        <!--
+            Activities for WebAPKs.
+        -->
+        <activity android:name="org.chromium.chrome.browser.webapps.WebApkActivity"
+            android:theme="@style/WebappTheme"
+            android:label="@string/webapp_activity_title"
+            android:launchMode="singleTop"
+            android:documentLaunchMode="intoExisting"
+            android:windowSoftInputMode="adjustResize"
+            android:persistableMode="persistNever"
+            android:hardwareAccelerated="false"
+            android:configChanges="orientation|keyboardHidden|keyboard|screenSize|mcc|mnc|screenLayout|smallestScreenSize">
+        </activity>
+        <activity-alias android:name="com.google.android.apps.chrome.webapps.WebApkActivity"

[gone, 2016/05/25 21:50:13]

Don't need this alias.

[Xi Han, 2016/05/26 17:23:35]

I thought the alias was for different channels of Chrome. Just out of curiosity,
 when to use the alias for the webappActivity?

[gone, 2016/05/26 18:20:36]

You should only use an alias when an Activity's file gets moved after it has
already been exposed to users.  In this case, when we upstreamed WebappActivity,
it moved from com/google/android/apps/chrome/webapps/WebappActivity.java to
org/chromium/chrome/browser/webapps/WebappActivity.java

+            android:targetActivity="org.chromium.chrome.browser.webapps.WebApkActivity"
+            android:label="@string/webapp_activity_title">
+        </activity-alias>
+        {% for i in range(10) %}
+        <activity android:name="org.chromium.chrome.browser.webapps.WebApkActivity{{ i }}"
+            android:theme="@style/WebappTheme"
+            android:icon="@mipmap/app_shortcut_icon"
+            android:label="@string/webapp_activity_title"
+            android:launchMode="singleTask"
+            android:windowSoftInputMode="adjustResize"
+            android:persistableMode="persistNever"
+            android:hardwareAccelerated="false"
+            android:taskAffinity="{{ manifest_package }}.webapps.WebApkActivity{{ i }}"
+            android:configChanges="orientation|keyboardHidden|keyboard|screenSize|mcc|mnc|screenLayout|smallestScreenSize">
+        </activity>
+        <activity-alias android:name="com.google.android.apps.chrome.webapps.WebApkActivity{{ i }}"

[gone, 2016/05/25 21:50:13]

You don't need this alias; it's only necessary for WebappActivity because we
changed the package name at some point.

[Xi Han, 2016/05/26 17:23:36]

Same question as above. WebApkActivity looks similar to WebappActivity, why
don't we need to change their's package name?

+            android:targetActivity="org.chromium.chrome.browser.webapps.WebApkActivity{{ i }}"
+            android:icon="@mipmap/app_shortcut_icon"
+            android:label="@string/webapp_activity_title">
+        </activity-alias>
+        {% endfor %}
 
         <activity android:name="org.chromium.chrome.browser.media.remote.ExpandedControllerActivity"
             android:theme="@style/MainTheme"