The issue comes from the fact that the Device Simulator
in both clients uses the same Cache
folder to keep the files it needs to work with. However, sometimes when you run the project from both clients, the core plugin files the Simulator
needs are not properly loaded in the cache. This is why the navigator.splashscreen call is unsuccessful - the Simulator
cannot find and load the SplashScreen
plugin from its cache and instead displays an error.
The Simulator Cache
is held in the Cache
folder under AppData\Local\Telerik\BlackDragon
and this is why clearing the entire folder helped. Basically as soon as the Cache
folder is cleared, AppBuilder
will recreate its content when loaded and the Simulator
will also be able to re-download the files it needs the next time it starts. I would, therefore, recommend in future if you encounter the same issue to only clear out the AppBuilder
cache on your machine.
I can understand how this might be an inconvenience for you but we usually do not recommend working simultaneously with both clients as this may cause issues with the livesync feature and the simulator
. Still, we are discussing options to improve the Simulator
behavior to minimize issues with the files in the cache.