Ensure newly created vaults are unlocked (#155)

A new vault should be unlocked after being created, because the
password is submitted as part of creating the vault. This was
accidentally broken as part of #148. A unit test has been added to
ensure this doesn't happen again.

Author: Gudahtt

index.js

@@ -80,7 +80,7 @@ class KeyringController extends EventEmitter {
   async createNewVaultAndKeychain(password) {
     await this.createFirstKeyTree(password);
     await this.persistAllKeyrings(password);
-    this.setUnlocked.bind();
+    this.setUnlocked();
     this.fullUpdate();
   }
 

test/index.js

@@ -85,7 +85,7 @@ describe('KeyringController', function () {
   });
 
   describe('createNewVaultAndKeychain', function () {
-    it('should set a vault on the configManager', async function () {
+    it('should create a new vault', async function () {
       keyringController.store.updateState({ vault: null });
       assert(!keyringController.store.getState().vault, 'no previous vault');
 
@@ -95,6 +95,15 @@ describe('KeyringController', function () {
       expect(vault).toBeTruthy();
     });
 
+    it('should unlock the vault', async function () {
+      keyringController.store.updateState({ vault: null });
+      assert(!keyringController.store.getState().vault, 'no previous vault');
+
+      await keyringController.createNewVaultAndKeychain(password);
+      const { isUnlocked } = keyringController.memStore.getState();
+      expect(isUnlocked).toBe(true);
+    });
+
     it('should encrypt keyrings with the correct password each time they are persisted', async function () {
       keyringController.store.updateState({ vault: null });
       assert(!keyringController.store.getState().vault, 'no previous vault');