-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible error in Fruitdown? #12
Comments
What browser is this occurring on? And if you're looking for the source, it's in pouchdb itself: https://github.com/pouchdb/pouchdb/blob/e1af762edf8cefe87a97b56f1095c5ca04310b30/packages/node_modules/pouchdb-adapter-leveldb-core/src/index.js#L908 |
If data is undefined it's probably a bug in Safari; supposedly all IDB bugs are fixed in Safari 10.1 but maybe a few more slipped through. Reason I say I doubt it's a bug in PouchDB is because that particular adapter passes the full PouchDB test suite against localstoragedown, fruitdown, memdown, and leveldown, so it seems unlikely to me |
Thanks for pointing me to the source, couldn't find it using github search box. I checked my logs, it's happening on ios mobile safari 10.2.1 and 10.0.2, using the fruitdown adapter, for at least 2 unrelated users. The answer of what is happening is probably in the |
You'd have to set a breakpoint and log the error to see what's going on; unfortunately throwing will do nothing because it's an async stack. |
In my logs I frequently get an error:
TypeError: undefined is not an object (evaluating 'n.doc._rev=n.value.rev')
This error points to
pouchdb.fruitdown.js
which points me here:I'm trying to find the root cause, but I am having a hard time finding the source of this code. Can you maybe help where
allDocsInner()
is defined? It's in the build of fruitdown, but not in this repo. In PouchDB there's anallDocsInner()
function too, but with a different signature.My wild guess now is indexeddb throws some kind of an error, but that error is not handled. See in the source above where I added
this line looks suspicious
.Hope you can help, thanks!
The text was updated successfully, but these errors were encountered: