"One of the specified object stores was not found." exception when using precaching

[jeffposnick]

Library Affected:
workbox-precaching

The original details from @beatrizdemiguelperez's report in our Slack channel:

I get this error on workbox-build v3-alpha2

Uncaught (in promise) DOMException: Failed to execute 'transaction' on 'IDBDatabase': One of the specified object stores was not found.
   at result (http://localhost:4200/workbox-v3.0.0-alpha.2/workbox-core.dev.js:1275:32)
    at new Promise (<anonymous>)
    at http://localhost:4200/workbox-v3.0.0-alpha.2/workbox-core.dev.js:1274:28
    at Generator.next (<anonymous>)
    at step (http://localhost:4200/workbox-v3.0.0-alpha.2/workbox-core.dev.js:14:32)
    at http://localhost:4200/workbox-v3.0.0-alpha.2/workbox-core.dev.js:25:15
    at <anonymous>

my generated sw with workbox-build tool is like this

importScripts("workbox-v3.0.0-alpha.2/workbox-sw.js","assets/service-workers/prueba-bea.js");


workbox.setConfig({modulePathPrefix: "workbox-v3.0.0-alpha.2"});
workbox.core.setCacheNameDetails({prefix: "buzz"});

workbox.skipWaiting();
workbox.clientsClaim();


/**
 * The workboxSW.precacheAndRoute() method efficiently caches and responds to
 * requests for URLs in the manifest.
 * See https://goo.gl/S9QRab
 */
self.__precacheManifest = [
  {
    "url": "assets/app.css",
    "revision": "f1126d43afe8da100a141d151020596f"
  },
  {
    "url": "tests/index.html",
    "revision": "d9f6ce3d70c4ebd77f1e9f148df85cd6"
  }
].concat(self.__precacheManifest || []);

if (Array.isArray(self.__precacheManifest)) {
  workbox.precaching.suppressWarnings();
  workbox.precaching.precacheAndRoute(self.__precacheManifest, {});
}

workbox.routing.registerNavigationRoute("/index.html");

before that i was working with v2 and everything was ok

[jeffposnick]

The code associated with the stack trace is

workbox/packages/workbox-core/_private/DBWrapper.mjs

Line 228 in af47ff9

const txn = this._db.transaction(storeNames, type);

Given that service worker code, the only thing that should be touching IndexedDB is workbox.precaching.

The facts that the developer is explicitly calling workbox.core.setCacheNameDetails({prefix: "buzz"}), and that they were moving from v2 to v3, might be relevant with regards to IndexedDB state.

@beatrizdemiguelperez, are you able to reproduce the issue when starting fresh from an Incognito window? And if so, can you deploy your web app at a public URL that we could visit?

[philipwalton]

It seems likely that a previous version of the IndexedDB database exists with the same name (i.e. one created by Workbox v2 code), so when the v3 Workbox code is running, its onupgradeneeded callback is never invoked, and thus the new object stores aren't created.

Perhaps the issue is here?
https://github.com/GoogleChrome/workbox/blob/09f6340/packages/workbox-precaching/models/PrecachedDetailsModel.mjs#L42-L44

Regardless, if we're using the same DB names from before the DBWrapper helper class was added, we shouldn't be reusing DB versions.

[gauntface]

I'll dig into this today and try and repro from old to new Workbox. Sounds like just using a new version number and managing the upgrade will be enough.

[beatrizdemiguelperez]

Hi @gauntface,

As you said from an incognito window it worked with alpha version.

Now i tried these changes on v3 branch and it works perfectly, so bug is fixed.

When will you publish v3 tag or next alpha?

Thanks!!

[jeffposnick]

Hello @beatrizdemiguelperez—While this isn't always the case, we try to stick to a bi-weekly release schedule.

As per https://developers.google.com/web/tools/workbox/community#team_calendar, the next release should go out on Thursday.

(During the alpha/beta period, those releases might not always match up, but that's the rough idea.)