Hi everyone,
I’m getting the following error while...
# suitecommercel
LC
11/03/2023, 6:01 PMHi everyone,
I’m getting the following error while trying to fetch the Extension of a Suitecommerce
(node:89214) UnhandledPromiseRejectionWarning: Error: Invalid login attempt.m
Martin
11/03/2023, 6:15 PMYou may need to give some more details, like gulp, npm, node versions. If you are using SC or SCA, and what version.
Martin
11/03/2023, 6:16 PMIf your Employee have the right roles, token, etc.
l
LC
11/03/2023, 6:41 PMIt’s an SC 2023.1.3, I’m using Admin role. And I already checked the token and integration record being created..
The full error is this one:
[153709] Continue the authentication process in the prompted browser.
(node:90600) UnhandledPromiseRejectionWarning: Error: Invalid login attempt.
at OAuth1._baseStep (/Users/Documents/Repos/extensions/ns_npm_repository/oauth1/index.js28719)
at processTicksAndRejections (internal/process/task_queues.js975)
at async OAuth1.issueToken (/Users/Documents/Repos//extensions/ns_npm_repository/oauth1/index.js35338)
at async authorize (/Users/Documents/Repos/extensions/gulp/ns-deploy/net.js33324)
(node:90600) 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=strictm
Mitchell Mudd
11/03/2023, 7:42 PMWhat node version are you using and do you have your integration record credentials loaded into the .env file?
l
LC
11/03/2023, 7:49 PMi’m using node 14.9 and yes, I added the integration record credentials to the .env
LC
11/03/2023, 7:50 PMshould I be using a different node version? I don’t know what else to try
m
Mitchell Mudd
11/03/2023, 7:52 PMl
LC
11/03/2023, 7:53 PMI’m sorry.. it was a typo, I’m using the 14.19.0 version
m
Mitchell Mudd
11/03/2023, 7:53 PMThis article covers how to setup the integration record (I definitely set it up wrong the first time). Make sure you have the integration record info in the .env file
https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1509997459.html#Set-Up-Theme-Developer-Tools
Mitchell Mudd
11/03/2023, 7:54 PMAnd earlier I had to recreate my integration record for some reason 🤷🏻♂️ so you could always try that
l
LC
11/03/2023, 7:58 PMI just did.. but still having the same error 😞
m
Mitchell Mudd
11/03/2023, 8:00 PMI don’t know if this would help but you could potentially run extension:fetch —to (two hyphens) and make a new authID using the credentials in your .env
l
LC
11/03/2023, 8:02 PMyeah.. still not working. I’m having really bad luck with this today.
LC
11/03/2023, 8:02 PM@Flo do you know if there is any other known issue related to fetching extensions with the latests tools?
f
Flo
11/03/2023, 8:05 PMNot that I am aware. Are you using npm?
Flo
11/03/2023, 8:08 PMTry deleting the consumer and secrety key from your env file and leave it blank. Then run a fetch -to
Flo
11/03/2023, 8:08 PMYou will get an error that the keys are missing
Flo
11/03/2023, 8:08 PMEnter the keys and try again
Flo
11/03/2023, 8:09 PMI remember that working for me once
l
LC
11/03/2023, 8:16 PMI just tested that and same error
f
Flo
11/03/2023, 8:23 PMTypically when i get errors in devtools is when i am not using the correct node version (i use nvm) and I installed gulp using a higher node version. I even ended up uninstalling nvm and installing everything from scratch 🤷🏻♀️
netsuite 1
Flo
11/03/2023, 8:24 PMI just checked and there are no errors reported for devtools
l
LC
11/03/2023, 8:39 PMI use nvm as well.
But this is the first time I’m getting this type of error 😞
I’ll need to try to uninstall everything
17 Views