AppBuilder Compatibility Issues, Client and VSExtension

Thread is closed for posting
4 posts, 0 answers
  1. matt
    matt avatar
    4 posts
    Member since:
    Aug 2013

    Posted 21 Aug 2014 Link to this post

    When we move our files from the AppBuilder Windows Client to the AppBuilder VS Extension Project the project runs fine and the simulator works fine running our application as intended out of Visual Studio until the following scenario takes place:

       When we run the project once again in the windows client (still using its original checked in code) the client still runs fine and our application still runs fine from the client but the Visual Studio project  never runs again in the simulator from Visual Studio. Even the template project that comes with AppBuilder never runs again. It doesn't matter if I reboot the machine, uninstall the windows client, uninstall the VS extension and reinstall the VS extension. The template project that comes from AppBuilder for Visual Studio never runs again in the simulator. We get a 'Cannot call method hide of undefined' for the line of code in the template project app.js file for navigator.splashscreen.hide();

    So to summarise the process again we have:
    Telerik AppBuilder WIndows Client installed (latest version up to date) with a working appbuilder project running fine
    and VS AppBuilder Extension installed in VS2013

    Then we:
    Create a new AppBuilder Project in VS2013
    Copy the files across from our Windows Client Project from an export of that project (obviously not the proj file)
    Run the project in VS2013 using the extension (all runs fine in the simulator)
    We once again run the old existing project that still runs fine in the Windows AppBuilder Client
    That runs fine in the simulator from the Windows Client
    Once again we run the project we now have in the VS2013 project from the VS Extension. It never runs again (reference errors etc., seems like bootstrapper never runs).
    And as mentioned even creating a new blank VS2013 AppBuilder template project never runs again out of the box.

    We have tried uninstalling everything, rebooting but all to no avail, the error seems to permanently persist now in that we cannot run anything again from VS2013 using the VS extension

    We are not sure how to rectify this issue, that seems to have permanently screwed up being able to run any AppBuilder project from Visual Studio again


  2. matt
    matt avatar
    4 posts
    Member since:
    Aug 2013

    Posted 21 Aug 2014 in reply to matt Link to this post

    So it appears that clearing the whole AppData\Local\Telerik\BlackDragon folder allows the simulator to run again correctly in Visual Studio. Surely we are not mean to do that every time we want to run something from the Windows Client AppBuilder and then be able to run something from the Visual Studio extension?
  3. Tina Stancheva
    Tina Stancheva avatar
    3299 posts

    Posted 22 Aug 2014 Link to this post

    Hi Matt,

    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.
    Tina Stancheva

    Visit the Telerik Verified Plugins Marketplace and get the custom Cordova plugin you need, already tweaked to work seamlessly with AppBuilder.

  4. matt
    matt avatar
    4 posts
    Member since:
    Aug 2013

    Posted 24 Aug 2014 in reply to Tina Stancheva Link to this post

    Hi Tina,

    Thanks for the quick reply. We will make sure we only clear out the AppBuilder cache.

Back to Top