Appbuilder CLI - Simulate Crashing

[mOpLin]

Please help, we have not been able to work from our enviroment.

Since the last update, when we try tu run the Simulate command, it opens and crashes. No message. 

Please help.

[Kaloyan]

Hello Pablo,

Could you check if deleting the AppBuilder cache folder solves the issue? For that purpose, you will need to open File Explorer and navigate to %localappdata%\Telerik\BlackDragon\Cache. Delete all of that folder's content and try running the simulator again.

If the issue still persists, we will need to know if there are any entries logged in the Windows Event Viewer for the Icenium.Simulator process. You will need to search in the Windows Logs > Application. The easiest way would be to reproduce the issue and then open the Event Viewer, as if any, the errors should be at the top of the list. If you find something, please share the error message in your next reply.

Regards,
Kaloyan
Telerik

 

 

[Evan]

@Kaloyan

Do you know where I could find the cache file on a Mac?

[Kaloyan]

Hello Evan,

On Mac, the Simulator's cache is found under:
/Users/{USER}/.local/share/Telerik/BlackDragon

And the AppBuilder's CLI cache:
/Users/{USER}/.local/share/Telerik/BlackDragon/.appbuilder-cli/Cache

You can delete both these folders in order to download the latest bits on your side. I hope this helps.

Regards,
Kaloyan
Telerik

 

 

[mOpLin]

Sorry for the delay, I havent been able to use the cli, I really need it now.

I couldn send the Event.evtx file.

[mOpLin]

Already tried uninstaling and installing everything again. (Node, and CLI)

[Kaloyan]

Hi Pablo,

This seems like a known issue in the AppBuilder Command Line Interface, that is already fixed in the upcoming AppBuilder 2.10 release. Until the new version is live, you can check if disabling the feature usage tracking will correct the AppBuilder Simulator behavior on your side. For that purpose, you will need to execute the following command:

$ appbuilder feature-usage-tracking disable

Please, let me know of the results.

Regards,
Kaloyan
Telerik

 

 

[mOpLin]

No luck, keeps crashing. 
Sorry

[Kaloyan]

Hi Pablo,

Could you try one more thing? Open File Explorer, navigate to the AppBuilder commands folder: C:\Users\<Your user name>\AppData\Roaming\npm\node_modules\appbuilder\lib\commands and replace the simulate.js file with the one attached to my reply.

Then, restart Command Prompt and check if the issue will reoccur. I hope this helps. Please, let me know of the results.

Regards,
Kaloyan
Telerik

 

 

[mOpLin]

Thank you, finally it did the trick. 
Its working again.

[Kaloyan]

Hi Pablo,

I am glad to hear this.

We also released AppBuilder 2.10 on Monday, which introduces the official fix for the issue you were experiencing. Please, let me know if you have further problems after updating the Command Line Interface on your side.

Regards,
Kaloyan
Telerik