Resolved promise unnecessarily and indefinitely maintains loading state

[LewisHarman]

When using updateDoc in Firebase, the promise is resolved promptly. This was realised in testing by refreshing the page to see if the updateDoc is reflected in the next query from the page and by console logging the returned data in a then statement connected to the custom asynchronous function executed inside the toast.promise. However, toast.promise does not detect the custom asynchronous function has been resolved ever and remains in a loading state indefinitely, rather than changing to a success or error state. I cannot replicate the issue on my device and everything works as expected and intended there. However, I do have a screenshot from 1 of 7 external colleagues who recently had this issue on their device. The toaster was so full it covered the whole screen, causing the external colleague to send a complaint. I believe they are using the latest stable release of Google Chrome, as of 11 April 2024, but cannot be certain about device, although likely a MacBook Pro or Windows 11.