Fix V1 app crash when verifying sockets API is available.

remoting/webapp/session_connector.js

 // Copyright 2013 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.
 
 /**
  * @fileoverview
  * Connect set-up state machine for Me2Me and IT2Me
  */
 
 'use strict';
@@ skipping 353 matching lines @@
    * @param {string} email
    */
   function connectSignalingWithTokenAndEmail(token, email) {
     that.signalStrategy_.connect(
         remoting.settings.XMPP_SERVER_ADDRESS, email, token);
   }
 
   // Only use XMPP when TCP API is available and TLS support is enabled. That's
   // not the case for V1 app (socket API is available only to platform apps)
   // and for Chrome releases before 38.
-  if (chrome.socket.secure) {
+  if (chrome.socket && chrome.socket.secure) {
     this.signalStrategy_ = /** @type {remoting.SignalStrategy} */
         (new remoting.XmppConnection(this.onSignalingState_.bind(this)));
   } else {
     this.signalStrategy_ = /** @type {remoting.SignalStrategy} */
         (new remoting.WcsAdapter(this.onSignalingState_.bind(this)));
   }
 
   remoting.identity.callWithToken(connectSignalingWithToken, this.onError_);
 };
 
@@ skipping 200 matching lines @@
  * Normalize the access code entered by the user.
  *
  * @param {string} accessCode The access code, as entered by the user.
  * @return {string} The normalized form of the code (whitespace removed).
  */
 remoting.SessionConnector.prototype.normalizeAccessCode_ =
     function(accessCode) {
   // Trim whitespace.
   return accessCode.replace(/\s/g, '');
 };