Fluent Player throws repeated “provider destroyed” unhandled promise errors during SPA navigation

I’ve been investigating repeated console errors during normal FluentCommunity SPA navigation:

Uncaught (in promise) provider destroyed

The errors originate from:

fluent-player.js?version=2.7.7

I traced the behavior in the installed Fluent Player runtime.

The Vimeo and YouTube provider destroy() paths explicitly reject unresolved provider command promises with:

provider destroyed

During normal Vue route navigation:

1. the Fluent Player custom element is removed;
2. disconnectedCallback() runs;
3. the player/provider is destroyed;
4. any pending provider RPC promises are rejected;
5. those rejections appear as uncaught promise errors in the browser console.

A single route change can produce multiple errors because several provider commands may still be pending at teardown.

I have not found evidence that the player runtime is duplicated or that my custom integration is double-initializing the same player. The errors also occur across several different SPA route transitions.

Playback appears to continue working normally, so this looks like an unhandled cancellation/teardown rejection rather than a functional playback failure.

Could you please confirm whether this is a known issue in Fluent Player 2.7.7?

It seems the provider teardown path may need to treat outstanding RPC cancellation as an expected handled condition rather than allowing the rejected promises to surface as unhandled errors.

I can provide stack traces or reproduction steps if helpful.