Uncaught (in promise) error when clicking links whilst a visit is in-flight
See original GitHub issueThis is most noticeable when pausing rendering for animations: if your click a link then tap another whilst that one is in-flight, an Uncaught (in promise)
error is thrown, originating here:
https://github.com/hotwired/turbo/blob/2332d3d0153886ff0c616198e377687a76ac5226/src/core/drive/visit.ts#L188 ~I think this.resolvingFunctions
is undefined
~
In 7.2.0-beta.2 this results in console errors. In 7.2.0-rc.1, rendering fails.
Looks like it might be something to do with: https://github.com/hotwired/turbo/pull/650? /cc @seanpdoyle
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Uncaught (in promise) undefined - Vue-router - Stack Overflow
I think the issue is being caused by the re-reoute. If the user does not have page_access 1, it then routes to /holidays....
Read more >"Store reset while query was in flight(not completed in ... - GitHub
Currently, queries are getting stuck in the QueryManager.fetchQueryPromises Map when stopQuery is called while that query is in flight.
Read more >login:1 uncaught (in promise) - You.com | The Search Engine You ...
I ran into a case that <router-link> was working fine, but router.push was complaining. (I think router-link internally suppresses such errors.) Solution ...
Read more >WebGL Player broken on Chrome 86.0.4240.75 - Unity 2019.4 ...
Try doing a Release build with --profiling-funcs enabled, to get a better callstack of the error. See the attached script for how to...
Read more >chrome.webRequest - Chrome Developers
Use the chrome.webRequest API to observe and analyze traffic and to intercept, block, or modify requests in-flight. Permissions. webRequest.
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 FreeTop 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
Top GitHub Comments
This sounds related to the problem reported in #706 (see https://github.com/hotwired/turbo/issues/706#issuecomment-1235188847)
I’m not seeing the error anymore after 1ec72ac3236038af50a0010f0821e0664eeac087 👍.