-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Something went wrong with 'Set Up Account'. #716
Comments
Hi @JJ0011 sorry about the experience you had. Is there a message in the 'Output' window of vscode? A 'see details' when the notification appears? |
Yea, same. Sorry @tourajvaziri but there's nothing in the output or additional info. Just the message as Ryan has shown. VSCode 1.78.0 |
Hi @JJ0011, @ryan-gillies and Sameul-Dainton Please provide us the specific info about your environment:
A screenshot of your project hierarchy (tree view) may also be useful. We haven't been able to reproduce your error for the SuiteCloud: Set Up Account command, so we are going to ask for some steps that may help to solve the issue.
After installing the v1.3.2 trigger again the SuiteCloud: Set Up Account command again and let us know about the result. As a workaround you can also install the node suitecloud CLI and setup the account for your project from the command line by running suitecloud account:setup |
Add Dependency returns the same error with no additional info, see details
or anything in the output.
Windows 11 Pro
VS Code 1.78.0
Extension 1.4.2
Java Version 8 Update 371 (build 1.8.0_371-b11)
1.3.2 does appear to work. I'm afraid I'm just about to log off for the day
to go through it fully.
Reverting back to 1.4.2 does not fix the issue.
I'll be sure to give the workaround a try once I have the time. Appreciate
the help!
All the best~
[image: image.png]
…On Fri, May 5, 2023 at 3:45 PM David Rebolleda Mir ***@***.***> wrote:
Hi @JJ0011 <https://github.com/JJ0011>, @ryan-gillies
<https://github.com/ryan-gillies> and Sameul-Dainton
Please provide us the specific info about your environment:
- *OS type and version* - Please do not extract this info from vscode
about section, we just want to know type of OS and its main version like:
Windows 10 Pro, MacOS Ventura 13.2.1 or Fedora Linux 38 (Workstation
Edition)
- *vscode version*
- *suitecloud extension version*
- *java version*
A screenshot of your project hierarchy (tree view) may also be useful.
We haven't been able to reproduce your error for the *SuiteCloud: Set Up
Account* command, so we are going to ask for some steps that may help to
solve the issue.
1.
Please try to run the *SutieCloud: Add Dependency References to the
Manifest* command.
Does it works succesfully? If it doesn't work, please take a
screenshot of the error notification and if the *See Details* button
appears also the related logs.
2.
Let's install a previous version (1.3.2) of the suitecloud extension.
To install a previous extension version:
Select extension section of the activity bar (icon similar to a tetris
piece)
Select the SuiteCloud Extension
Click on the drop down context menu at the side of the Uninstall button
Select version 1.3.2
Reload vscode
After installing the v1.3.2 trigger again the *SuiteCloud: Set Up Account*
command again and let us know about the result.
Once you are done with this tryout you can restore the suitecloud
extension to latest version.
As a workaround you can also install the node suitecloud CLI and setup the
account for your project from the command line by running *suitecloud
account:setup*
To install suitecloud-cli please check:
https://github.com/oracle/netsuite-suitecloud-sdk/tree/master/packages/node-cli
—
Reply to this email directly, view it on GitHub
<#716 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYBMVBNICJL3RT56PAJVP43XEUHA5ANCNFSM6AAAAAAXJDMENQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Oh that's odd. Came back today to try out the 1.3.2 and it's now having the same issue. >_< |
I created a new project and it appears to be working now. The error appears to be caused by creating a project with jest testing enabled. |
@Samuel-Dainton thanks for the info, we'll consider your provided info for further investigation. |
We have been able to replicate the error, thanks to the info provided by @Samuel-Dainton Source of the problem is that npm dependencies are not properly installed when creating a project from vscode-extension that includes support for unit testing. As a workaround you can manually install the dependencies from the terminal by running We'll track this bug to fix it. |
Has this been resolved yet? I am experiencing the same issue, when I create a SuiteCloud project and include JEST testing |
@nguyena-smartecarte @Samuel-Dainton @JJ0011 |
Is there any otther solution for this problem, I have had this error for a week. |
@hamayxx When you run |
Here is the output Btw, I have just installed a previous version of JDK (v1.4.1) then it works. Just wonder that what happened to these JDK version. |
Extension 1.4.2 with Java JDK 17.0.7 works... but newer extension or JDK doesn't. It even corrupts credentials file. |
Hi All, I'm ACS employee and I solved this issue with our customer. The solution was to ensure there is no space in a private key file path. It seems there a path is not enclosed in quotes when a command is built. |
Type: Bug
The SDF is properly configured.
There is an active file in the editor which belong to the current workspace. Before running this command, I have selected a file from the current workspace and make it active in the editor.
But whenever I run the command 'Set Up Account', I am getting the following error :
"Something went wrong with 'Set Up Account'."
Extension version: 1.4.1
VS Code version: Code 1.77.3 (704ed70d4fd1c6bd6342c436f1ede30d1cff4710, 2023-04-12T09:16:02.548Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: Yes
System Info
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
A/B Experiments
The text was updated successfully, but these errors were encountered: