Do the ThemeDevelopmentTools-18.2.1.zip and Extens...
# suitecommerce
k
Do the ThemeDevelopmentTools-18.2.1.zip and ExtensionDevelopmentTools-18.2.1.zip developer tools zip files in the SuiteCommerce Extension Management 2023.1.3 version bundle work? I am building an extension and modifying the theme for SCA Aconcagua release 2. I was working with the SuiteCommerce Extension Management 2023.1.3 developer tools zip files, but running in local development mode doesn’t work with the 2023.1.3 developer tools zip files. Installed the ThemeDevelopmentTools-18.2.1.zip developer tools. Now I am running into token authentication/login issues.
I created an access token using the “SC-TBA” integration and created an entry in .nstba:
Copy code
[14:55:36] Using gulpfile ~/tmp/SCA2018-Test/ThemeDevelopmentTools-18.2.1/gulpfile.js
[14:55:36] Starting 'theme:fetch'...
? Choose a saved token TEST-TOKEN
[14:55:39] Using token TEST-TOKEN, run with --to to change it
[14:55:39] 'theme:fetch' errored after 3.07 s
[14:55:39] StatusCodeError in plugin "gulp theme:fetch"
Message:
    401 - {"error":{"code":"INVALID_LOGIN_ATTEMPT","message":"Invalid login attempt."}}
Details:
    statusCode: 401
    error: [object Object]
    options: [object Object]
    response: [object Object]
The role that I am using with the access token is Administrator, so I don’t think it’s a role or permissions issue.
👀 1
I discovered the Invalid Login Attempt error appears to only occur with the sandbox. Not production. I chacked the SCA-TBA integration record, the access token and the script deployment records. They are configured the same. The access token is using the Administrator role. Anyone have an idea why the sandbox would return an invalid login attempt and the production account would not. Both accounts are NetSuite 2023.2. I have had to modify the ThemeDevelopmentTools-18.2.1 gulp/node files in a couple of places. One of these places is to replace the underscore in the account ID with a dash. Anyone have ideas.?