Hi Hugo,

Thank you for sharing this issue with us.

May I please ask you to check if the same issue is reproduced when you open your Lightning files using the Lightning Bundle Explorer? You can navigate to this panel from the menu View.

Also, please let me know if this applies to all your Lightning files or for some type of members/some bundles?

Also, I kindly ask you to reproduce the issue one more time and send us a bug report with the attached log files directly from the IDE - you can find this functionality in the menu Help -> Report a Bug, please put your email and enable the 'Attach Log File' checkbox. This way we would receive your TWS log files which could provide us with an additional information about a reason for the issue.

Looking forward to your response and to a bug report from you.

Thank you,

Kate

Hi Everyone!
I have the same problem now. Lightning Bundle Explorer doesn't work as well and even more it throws a system exception and aborts whole application when I'm trying to open Lightning Component. I've generated bug report and sent it to you.

Thanks,
Vadim

Hi Vadim,

Thank you for your post and for the bug report from you.

According to your TWS log files, a reason for the issue is related to your the connection to your org.

I kindly ask you to refresh or update your credentials in the project's properties or please re-authorize if you used OAuth authentication during the project creation.

Our developers are looking for a reason for such behavior and for a way to handle this case.

Please let me know if updating your credentials would help to solve the issue.

Thank you,

Kate

Hi, Kate!
I've changed my credentials on the org, created new project in Welkin from the scratch and authorized there, but it still has the same issue. FYI: Apex classes and Lightning Events opens good, the problem only related to Lightning Components.
Thanks,
Vadim

Hi Yes same thing on my side. 

On my company we are now using the TWS and for 5 users is the same error. Using the R18 installation. But I have a colleague from a different company that has no problem opening the Lightning Components.

Thanks

Hi guys,

Thank you for your responses and all the details.

We are looking for a reason for this issue, and may I please ask you several more questions so that we clarify some information?

Here are the questions:

     1. First of all, I kindly ask you to open the Lightning Bundle Explorer, and please check if all the members are present in the component bundle which cannot be opened properly? In other words, if all the included to the component bundle file are displayed in the list?

     2. Also, can you please let me know if you used OAuth type of authentication or regular credentials (login, password, and security token) when you created your project where the issue is reproduced? Do you use the 2 factor authentication on your org?

     3. What type of environment are you working on: is it a sandbox, developer edition, or production?

Looking forward to your response and we will be happy to solve the issue as soon as possible.

Thank you,
Kate

Hi, 

1. It is empty... I just can create new ones, I cannot load the existent ones
2. I'm using login pass and token
3. Is a Full Sandbox

I've the last version of TWS (v1.19.9.4), is it possible to install a previous one to test?

Because I'm pretty sure that was working before.

Thanks

Hugo Costa

Hi, 

Just adding one more thing, with the same TWS I open a different project from a Developer Sandbox, and it works fine... 

Is this restricted for the type of environment??

Thanks

Hi, Kate!
1. I see list of components in Lightning Boundle Explorer but when I'm trying to open one of them- Welkin crashes.

2. I'm using regular credentials (login, password, and security token) .

3. I'm in Developer Edition org.

Thanks,
Vadim

Hi guys,

Thank you greatly for your responses!

We continue to investigate this issue, and I have one additional question - do you have a namespace on your organization related to the project where the issue is reproduced?

Also, we would appreciate if you could send us your refreshed TWS log files after updating credentials. You can do this ending a bug report directly from the IDE.

I will share the installer of the previous TWS version via email.

I want to draw your attention that after the installation of Bloom R17 version of the IDE, this is necessary to disable the auto-update functionality so that the IDE won't be updated to Bloom R18. For this, please open your Task Manager -> Services -> Services..., find the 'The Welkin Suite Auto-Updater' service, right-click on it and open the 'Properties' item. Please change the Startup type to the Disabled value.  

Thank you for your collaboration!

Best Regards,

Kate

Hi Kate,

Just installed the old version and I have the same error.

Also sent the bug using the TWS "Report a Bug", and sending also the print screen of the error.

Thanks

Best regards

Hi, Kate!
I've just uninstalled BloomR18 and when I'm trying to install BloomR17 it shows me following error. Do you have an idea how to fix that?

Hi, Kate!
In addition to my previous post- I've tried to install the newest Bloom R18 again and it prevents me from installation too. Please see screenshot.
Thanks,
Vadim

Hi guys, 

Thank you for your responses.

Vadim, in this case, please follow the next steps to uninstall the IDE using a command line:
 1) please open your Regedit (Registry Editor) and the next path in it: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\The Welkin Suite\TheWelkinSuite\1.0;
 2) copy a value of a Product Code parameter;
 3) run cmd and execute the next command: MsiExec.exe /x {ProductCode Value}

As a result, TWS would be removed from your computer and you would able to install the IDE again.

As for the issue when opening Lightning components, may I please summarize a little bit and clarify some more details?

     - the issue is reproduced for some organizations with different environment types;

     - this is reproduced on the previous version of the IDE where you could open lightning files successfully earlier;

     - this applies to all the lightning components files in TWS project (where the issue is reproduced).

Here are my additional questions:

     1. I kindly ask you to check if the files which you cannot open are present locally: you can easily navigate to your project folder using the 'Open Folder in File Explorer' in the context menu of your project in the Solution Explorer in TWS, please find the subfolder 'src' and then 'aura'.

     2. Can you please check if there are any errors in your Event Viewer when this issue is reproduced in the IDE? To find this, please follow the next steps:
         1) open you Event Viewer / Windows Logs / Application.;
         2) please check if there are any errors related to The Welkin Suite - you can find this in a description of an error;
         3) if such errors exist, please open their details in the 'XML View' and send this data to us; also please share with us general information about these errors.

     3. Do you have a namespace on your org?
      

Also, after the installation of Bloom R17 version of the IDE, I kindly ask you to create a new project and check if the issue would be reproduced for this project.

We continue our investigation and I want to tell you one more time that we greatly appreciate your collaboration!

Thank you,

Kate

Hi, 

I was able to install the TWS 17 version and I have the same issue. 

But trying a different approach, I'd create a new project but instead of link to Dev environment I set to the UAT environment - and it works fine .

• Dev - (Full Sandbox)
• UAT - (Full Sandbox)

Once they are the same type could it be some type of confuguration/permission?

Thanks

Best regards

Hugo Costa

Hi Hugo,

Thank you for your update and for your investigation and please sorry for such delay in my response.

Yes, in this case, we can see that since files are the same on both your organizations, the issue can be caused exactly by configuration or permission differences.

We will keep our eye on this issue.

Also, we would greatly appreciate any additional information if any and we will be happy to find a reason for this and solve it.

Thank you for your collaboration!

Best Regards,

Kate