Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
AbortError: AbortError
See original GitHub issueI’m getting an error like this:
Vue warn]: Error in v-on handler (Promise/async): "AbortError: AbortError"
No other information given.
I’m simply trying db.instance.add("<storageName>", payload). The DB exists. How can I get more information about what’s wrong?
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Unhandled Rejection (AbortError): The operation was ...
From MSDN: Note: When abort() is called, the fetch() promise rejects with an Error of type DOMException, with name AbortError.
Read more >AbortController.abort() - Web APIs | MDN
The reason why the operation was aborted, which can be any JavaScript value. If not specified, the reason is set to "AbortError" ...
Read more >AbortError - 4.7 - Ember API Documentation
A AbortError is used by an adapter to signal that a request to the external API was aborted. For example, this can occur...
Read more >Dexie.AbortError
When catching AbortError, always inspect the property inner to gain more information about the reason why the transaction was aborted.
Read more >AbortError class - Microsoft Learn
Error thrown when an action is aborted. In this article. Constructors; Properties; Constructor Details; Property Details. Extends. Error ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think the fix is as simple as https://github.com/jakearchibald/idb/commit/24e7d91cae412f4205a9cf8d5cfd9ab56fc7f311 - which means the error from the
put/add/whatever takes priority over the error from the transaction. I need to write some tests for this before landing it.Without a minimal reproduction from any of the reporters here, it’s possible I’m tackling a completely different issue. If that’s the case, please create a minimal reproduction of the issue you’re seeing.
Fixed in https://github.com/jakearchibald/idb/pull/181 and published as 5.0.3.
If this didn’t solve the issue, please reopen, but I won’t fix anything without a minimal reproduction of the issue.