<@UEU3GRP5M> or <@UAA1TMMTR> maybe you could help ...
# sdf
k
@Carlos Olivares (NS DevTools PM) or @Albert Margarit (NS Eng Lead) maybe you could help with this?
a
This is typically an auth problem. We are fixing this to provide a meaningful message here.
k
Odd. Havent updated the tokens at all. Just got that message but changed to production on the project settings and all was ok.
a
That may be a bug then. Is that on Eclipse/Webstorm?
k
Webstorm.
It may be something I did wrong but wanted to bring it up to make you aware.
a
I assume sandbox and production are exactly the same domain, right?
or do you use account specific domains?
k
yep correct.
Same domain.
produced 2 lots of tokens for admin role one for sandbox and one for production.
Don’t currently use SDF for objects just for files for suitescript. FYI
a
So the reproduction steps are something like: - Set the sandbox account as the default for the project - Deploy using "deploy to account" and select a production account
Is this it?
k
Yep.
a
both using TBA?
k
yep
a
can't reproduce 😞
k
Not to worry. I fixed in the end by switching the project settings to production and then back again after deploy. Now the deploy to account works on both no issues regardless of project setup.
a
Ok
Thanks. Let me know if you find out what could be the problem
k
Will do.
One thing you need to fix is the SuiteCloud IDE SDF Logs popping up automaticaly when you deploy. it is very annoying.
👍 1
a
In WebStorm I guess, right?
k
yep.
WebStorm all the way with me.
c
this could be from a messed up deploy or manifest file as well