Skip to content
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

DbError, InvalidStateError on Firefox #779

Closed
armhub opened this issue Nov 15, 2018 · 2 comments
Closed

DbError, InvalidStateError on Firefox #779

armhub opened this issue Nov 15, 2018 · 2 comments
Labels
bug broken functionality, usability problems, unexpected errors state:tested We tested it and are about to release it
Milestone

Comments

@armhub
Copy link
Contributor

armhub commented Nov 15, 2018

DbError. could not create transaction: InvalidStateError, A mutation operation was attempted on a database that did not allow mutations.
Tutanota version: 3.38.6
User agent: 
Mozilla/5.0 (X11; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0

Stacktrace: 
DbError. could not create transaction: InvalidStateError, A mutation operation was attempted on a database that did not allow mutations.> value/<@https://mail.tutanota.com/worker.js:1:398228
r@https://mail.tutanota.com/libs.js:32:9667
[22][22][22]c@https://mail.tutanota.com/libs.js:30:1608
a@https://mail.tutanota.com/libs.js:30:1496
[2]r/this.drainQueues@https://mail.tutanota.com/libs.js:30:1236

DbError@https://mail.tutanota.com/common.js:1:176592
value/<@https://mail.tutanota.com/worker.js:1:398305
r@https://mail.tutanota.com/libs.js:32:9667
[22][22][22]c@https://mail.tutanota.com/libs.js:30:1608
a@https://mail.tutanota.com/libs.js:30:1496
[2]r/this.drainQueues@https://mail.tutanota.com/libs.js:30:1236

Originally posted by @charlag in #657 (comment)

@armhub armhub added this to the Out of beta (part I) milestone Nov 15, 2018
@armhub armhub added the bug broken functionality, usability problems, unexpected errors label Nov 15, 2018
@charlag
Copy link
Contributor

charlag commented Nov 15, 2018

MDN says that it occurs when

The close() method has previously been called on this IDBDatabase instance.

Which makes me think that it's the same as #452

@charlag charlag mentioned this issue Nov 15, 2018
@charlag charlag added the state:tested We tested it and are about to release it label Nov 16, 2018
@charlag
Copy link
Contributor

charlag commented Nov 16, 2018

assume tested

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug broken functionality, usability problems, unexpected errors state:tested We tested it and are about to release it
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants