Resolving Source Code Deployment Errors During Gulp Deploy

Issue: While deploying source code using gulp deploy, you may encounter the following errors:

1. INVALID_LOGIN_ATTEMPT Error

Error INVALID_LOGIN_ATTEMPT Invalid login attempt.

1. Exceeded Number of Active Access Tokens for Role

(node:6668) UnhandledPromiseRejectionWarning: Error: This user has exceeded the number of active access tokens for this role.
    at OAuth1._baseStep (C:AjithKsProjectsPCINPATCH EXTENSION CHECKWorkingsourceSC_23.1_LiveCommonsns_npm_repositoryoauth1index.js:287:19)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async OAuth1.issueToken (C:AjithKsProjectsPCINPATCH EXTENSION CHECKWorkingsourceSC_23.1_LiveCommonsns_npm_repositoryoauth1index.js:356:25)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:6668) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:6668) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[11:31:02] The following tasks did not complete: deploy, upload
[11:31:02] Did you forget to signal async completion?

Solution:

Step 1: Resolve INVALID_LOGIN_ATTEMPT Error

• Create a new authentication token in NetSuite.
• Navigate to Setup > Users/Roles > Access Tokens.
• Generate a new token and update your local .env file or authentication settings accordingly.
• Try deploying the source code again using gulp deploy.

Step 2: Resolve Active Access Tokens Limit Error

• If you encounter an error indicating that the maximum number of active access tokens has been exceeded:
• Navigate to Setup > Users/Roles > Access Tokens.
• Find the existing token associated with your deployment role.
• Deactivate the existing token.
• Create a new access token.
• Update your local authentication settings with the new token.
• Retry gulp deploy.

Following these steps should resolve the issue and allow for a successful deployment.