Skip to main content
added 81 characters in body
Source Link

At first sight, I Would say that this behavior (not executing the console.log) is due to you not handling errors with catch, try to add a catch statement and to console.log().

For the indefinite wait, it looks like a promise not resolving, meaning that it's in the indefinite state of pending, it is likely to be due again to the absence of catch statement : errors not being resolved.

I might be wrong on this one, feel free to correct me if you find the answer.

At first sight, I Would say that this behavior (not executing the console.log) is due to you not handling errors with catch, try to add a catch statement and to console.log().

For the indefinite wait, it looks like a promise not resolving, meaning that it's in the indefinite state of pending, it is likely to be due again to the absence of catch statement : errors not being resolved.

At first sight, I Would say that this behavior (not executing the console.log) is due to you not handling errors with catch, try to add a catch statement and to console.log().

For the indefinite wait, it looks like a promise not resolving, meaning that it's in the indefinite state of pending, it is likely to be due again to the absence of catch statement : errors not being resolved.

I might be wrong on this one, feel free to correct me if you find the answer.

added 296 characters in body
Source Link

At first sight, I Would say that this behavior (not executing the console.log) is due to you not handling errors with catch, try to add a catch statement and to console.log().

For the indefinite wait, it looks like a promise not resolving, meaning that it's in the indefinite state of pending, it is likely to be due again to the absence of catch statement : errors not being resolved.

At first sight, I Would say that this behavior is due to you not handling errors with catch.

At first sight, I Would say that this behavior (not executing the console.log) is due to you not handling errors with catch, try to add a catch statement and to console.log().

For the indefinite wait, it looks like a promise not resolving, meaning that it's in the indefinite state of pending, it is likely to be due again to the absence of catch statement : errors not being resolved.

Source Link

At first sight, I Would say that this behavior is due to you not handling errors with catch.