"Unexpected token in JSON at position 51" when running inside packaged Electron app

nolanlawson / pouchdb-electron

PouchDB for Electron (formerly Atom Shell)

128 stars 7 forks source link

"Unexpected token in JSON at position 51" when running inside packaged Electron app #8

Open linusthiel opened 7 years ago

linusthiel commented 7 years ago

We are using PouchDB-browser inside an Electron packaged app.

We package it for Windows, as an exe, using electron-packager.
We have two pouch dbs, one synced with a couch server and one local (just mapping ids to yet another local db)
When running it with electron . i.e. not packaged in an exe, everything works fine
When running it as the packaged Windows exe, the local (mapping) db throws "Unexpected token in JSON at position 51", i.e. is sending some garbage data when we do db.get(id)
Both running on the same system
The app is using the same dbs in "dev-mode" as in packaged mode
We paused the app in the debugger, and ran db.allDocs which worked fine
We detroyed the db and it is still throwing the same error on db.get, so it seems to be (at least) the 404 error having a problem.

linusthiel commented 7 years ago

We tried to reconfigure it to use different databases. It still gives the same error in the packaged Electron, when we do db.get(id).

Electron version 1.4.15 win32-ia32. PouchDB-browser version 6.1.1 Windows 10

nolanlawson commented 7 years ago

So this only happens on Windows, but it happens in multiple adapters - IndexedDB, WebSQL, etc.? I'm wondering if it's a bug in Chromium for Windows.

Can you provide a small test case to reproduce, e.g. a sample project?

linusthiel commented 7 years ago

I haven't tried WebSQL but I will. It's some weird thing definitely because it worked before, and we're not sure what has changed. Will try to make a test case when I get a minute to work on it!

On Jan 25, 2017 5:21 PM, "Nolan Lawson" notifications@github.com wrote:

So this only happens on Windows, but it happens in multiple adapters - IndexedDB, WebSQL, etc.? I'm wondering if it's a bug in Chromium for Windows.

Can you provide a small test case to reproduce, e.g. a sample project?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/nolanlawson/pouchdb-electron/issues/8#issuecomment-275172395, or mute the thread https://github.com/notifications/unsubscribe-auth/AXjYx5zxZgkHWBkuQHUeZMW2ndIFru8fks5rV4StgaJpZM4LtQWD .