- Electron version: 1.2.6
- Operating system: macOS 10.11.5, Windows 10 (issue verified in both)

Up to and including v1.2.2, closing an Electron application and reopening it would restore the session/cookies as it was previously. 

As of v1.2.3 (and still verified as an issue in v1.2.6), this is no longer the case. In our case users login to our application and get a cookie that allows them to continue using the app for a few weeks.

This may be tangental, but it seems that if the session was created by v1.2.2 or older, upgrading to v1.2.3+ retains that session. But as soon as it is cleared by v1.2.3+ and you try to login again, closing the app and reopening will always present the login screen, tossing the session that was created by the previous app instance.

atom/browser/api/atom_api_protocol.cc
#include "atom/browser/api/atom_api_protocol.h"
#include "atom/browser/atom_browser_client.h"
#include "atom/browser/atom_browser_main_parts.h"
#include "atom/browser/net/url_request_async_asar_job.h"
#include "atom/browser/net/url_request_buffer_job.h"
#include "atom/browser/net/url_request_fetch_job.h"
#include "atom/browser/net/url_request_string_job.h"
#include "atom/common/native_mate_converters/callback.h"
#include "atom/common/native_mate_converters/value_converter.h"
#include "atom/common/node_includes.h"
#include "atom/common/options_switches.h"
#include "base/command_line.h"
#include "base/strings/string_util.h"
#include "content/public/browser/child_process_security_policy.h"
#include "native_mate/dictionary.h"
#include "url/url_util.h"
using content::BrowserThread;
namespace atom {
namespace api {
Protocol::Protocol(v8::Isolate* isolate, AtomBrowserContext* browser_context)
    : request_context_getter_(static_cast<brightray::URLRequestContextGetter*>(
          browser_context->GetRequestContext())),
      weak_factory_(this) {
  Init(isolate);
}
void Protocol::RegisterServiceWorkerSchemes(