Handle authentication failures in the v2 app by restarting the app

remoting/remoting_webapp_files.gypi

Index: remoting/remoting_webapp_files.gypi
diff --git a/remoting/remoting_webapp_files.gypi b/remoting/remoting_webapp_files.gypi
index bc0aba74a64edc95a9df3c4238c1a7447e396283..1be8c382ab2ee482b85128d1a54f91ef5867717f 100644
--- a/remoting/remoting_webapp_files.gypi
+++ b/remoting/remoting_webapp_files.gypi
@@ -60,6 +60,8 @@
       'webapp/base/js/application.js',
       'webapp/base/js/base.js',
       'webapp/base/js/platform.js',
+      'webapp/base/js/remote_methods.js',

[Jamie, 2015/01/23 23:33:26]

Communicating between the main and background pages is not really "remote" (at
least, not in the context of a remote access application). I suggest calling
this something like ipc.js.

+      'webapp/crd/js/activation_handler.js',
       'webapp/crd/js/apps_v2_migration.js',
       'webapp/crd/js/error.js',
       'webapp/crd/js/event_handlers.js',
@@ -228,6 +230,8 @@
       'webapp/base/js/base.js',
       'webapp/base/js/message_window_helper.js',
       'webapp/base/js/message_window_manager.js',
+      'webapp/base/js/remote_methods.js',
+      'webapp/crd/js/activation_handler.js',
       'webapp/crd/js/app_launcher.js',
       'webapp/crd/js/background.js',
       'webapp/crd/js/client_session.js',