No stack trace on companion app

2 posts, 0 answers
  1. Tim
    Tim avatar
    20 posts
    Member since:
    Apr 2016

    Posted 24 Jun Link to this post

    I have been told that there is an issue with the Companion app which was recently updated. We no longer get a a stacktrace screen when we livesync to devices and test via the Companion app. Is anybody able to provide an ETA when the the next release of the companion app is going to be deployed?

    I'm using the in-browser client and testing via livesync. If I create a bug I have no idea what it was, so I'm coding and testing a line at time. So I've pretty much ground to a halt. Thanks, Tim




  2. Toma
    Toma avatar
    2 posts

    Posted 29 Jun Link to this post

    Hello Tim,

    Thank you for contacting us about this problem. I performed several tests and wasn't able to reproduce the issue. The new Developer Apps (formerly known as Companion Apps) along with the new Telerik Platform Companion App were recently released and are in the process of improving as developer tools. There are several known issues that are currently logged in the internal bug-tracking system and will be resolved within the current development cycle and published with the next release. You can refer to this documentation to install the latest versions of the companion apps.

    Here are the test case that I performed on both iOS and Android for NativeScript.
    1. Open Telerik Platform Companion App and login.
    2. Go to 'My Apps' and choose random NativeScript application. Tap on 'Open'.
    3. The application is loaded in the {N} Developer App and runs normally.
    4. Write syntactic error in app.js file and livesync.
    5. After the livesync is over, the {N} Developer App restarts and crashes due to the syntactic error (step 4).
    6. On next launch, a crashlog/stacktrace is displayed with options to 'reset' and 'sync'. 

    Regarding Cordova, at this stage there isn't implemented functionality that generates crashlogs / stacktraces. In iOS, you can debug javascript portion of your code using Safari. In order to do so follow these steps:
    1. Build the application using debug configuration and development provisioning profile.
    2. Deploy the resulting .ipa archive on a device and connect the device with machine running on Mac OS.
    3. Run the deployed application on the device.
    Open Safari , and from the Develop drop-down you should see the name of the connected device and the name of your app under Inspectable applications. Once you click on the application name, Safari Web Inspector should open and you should be able to debug the app. 

    Any information will be very helpful in order to further investigate the issue. It would be very useful if you could provide definite steps to reproduce the problem and also provide information about the OS and platform that you are developing against. 


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

Back to Top