Can someone share what I'm missing? The workaround shared by Joaquin doesn't seem to work for 2018.2 theme dev tools? index.js

OAuth1.prototype._step3 = function (account, token, verifier, secret) {
        var self = this;
        return new Promise(function (resolve) {
            var params = { account: account, token: token, verifier: verifier, secret: secret };
            resolve(self._baseStep("" + (self.vm ? '' : account.replace('_','-')) + self.urls.step3, params));
        });
    };

net.js

,   authorize: function(deploy, cb) {
        oauth1
            .issueToken(deploy.info.authID)
            .then(({ account }) => {
                deploy.info.account = account;
                if (args.vm) {
                    deploy.info.hostname = args.vm.replace(/https?:\/\//, '');
                } else {
                    const molecule = args.m ? `${args.m}.` : '';
                    deploy.info.hostname = `${account.replace('_','-')}.restlets.api.${molecule}<http://netsuite.com|netsuite.com>`;
                }

                log(
                    `Using token ${c.magenta(deploy.info.authID)} - Account ${c.magenta(
                        account
                    )}, run with --to to change it`
                );
                cb(null, deploy);
            });
	}

From what I have experienced.. you should just upgrade your dev tools.

@Kearobi Thanks, that's what I figured out as well, but won't that be an issue if let's say I'm using 2018.2? or an older version of SCA?

As far as I know the dev tools are backwards compatible. Last time I did this (SCA 2019.2 - SCEM 2018.2.1) I upgraded to SCEM 2020.2.1 and also Node to 12.x to support TBA. That all required a fresh NPM install, but no patch required.

That's weird because I found a note in SuiteAnswers saying that for 2018.2, you must strictly use the 2018.2 dev tools. Anyway, good to hear thank you!

Hi @ckipfler have you followed the patch guidelines? https://3667092.app.netsuite.com/app/help/helpcenter.nl?fid=article_161109340483.html