@dantcamui This error generally means that the version of the engine that you have installed does not recognize some of the tools used in your app. Running it in the same (or newer) VisionAppster release as the one the app was created with should fix it.

A bug fix for this popup problem amongst quite a few other fixes will be available in a couple of days in beta 6 release, stay tuned! Should anything similar ever happen, there is also a shortcut CTRL+S for saving the project, which may be worth a try.

@dantcamui This error generally means that the version of the engine that you have installed does not recognize some of the tools used in your app. Running it in the same (or newer) VisionAppster release as the one the app was created with should fix it.

Can you check for any errors visible in the message box when clicking the Messages button in the bottom bar? It would sound like there was an issue opening the file selection dialog in your system.

Hi,
you can use manager object's appStarted signal to reconnect the API when the app has been restarted:

const myAppId = 'com.myapps.testapp/1';
let apiCtrl;
let api;
let managerCtrl;
let manager;

async function connectApi()
{
  if (apiCtrl)
    apiCtrl.disconnect(); // Note: this is currently needed first
  apiCtrl = new va.RemoteObject('/apis/' + myAppId);
  api = await apiCtrl.connect();
}

async function connect()
{
  managerCtrl = new va.RemoteObject('/manager');
  manager = await managerCtrl.connect();
  manager.$appStarted.connect((appId) =>
  {
    if (appId === myAppId)
      connectApi();
  });
  connectApi();
}

Now, if you add connect() call before setInterval() call in your example, the api object should be always connected and ready to serve whenever the app is running.
P.S. there seems to be also an issue that the previous remote api object instance needs to be disconnected first, or reconnecting won't work. We'll be looking at
that also.