AppBuilder client don't see iPad connected

[Victor]

Having Windows 7, Telerik Appbuilder, iPad with iOS 9.1

 

Appbuilder don't see iPad connected  - "Cannot show properties when no device is selected"

 I read through the FAQ and tried to reset device pairing - no pairing detected, mobile options are empty

 

iPad in Windows itself is reachable, I can browse or download photos.

 

 

 

[Tina Stancheva]

Hello Victor,

Can you please check whether your machine has the latest version of iTunes installed. Also, make sure that iTunes recognizes the connected device before you try to see the apps running on it through the AppBuilder interface.

Here is the complete workflow for debugging a running AppBuilder hybrid app on a connected iOS device:

•  Download and install the latest version of iTunes, if not already installed.- to download iTunes, go to the iTunes section on the Apple website and click Download iTunes.
• Run the AppBuilder Windows client and open your project.
• Connect your device to your system via USB cable.
• If prompted, enter your password on the device to unlock it. Click OK to continue.
• If promoted, confirm on your phone that you trust the connected computer.
• In the AppBuilder status bar, click Show Mobile Devices and verify that AppBuilder lists your connected device.

Let me know if that helps.

Regards,
Tina Stancheva
Telerik

 

 

[Victor]

Thanks, iTunes helped

Now I can connect, but debugger crashed

from the log: 

[1126/143434:ERROR:renderer_main.cc(200)] Running without renderer sandbox

I'm trying to debug some mystical error on iOS application, but I can't because debugger crashes each time when this error occurs in the browser.

 

[Tina Stancheva]

Hi Victor,

The error in the log does not lead to the debugger crashing. The renderer sandbox is an optional protective feature for the web rendering code. The error is logged by CEF (the framework we're using in the DevTools window) and it can be ignored.

As for the debugger crashing, I am afraid that something in your code is causing the app to crash. I suppose at that time, the debugger is closed as it cannot run when the app dies. Unfortunately I am not aware of a good approach that would allow you to easily get the stack trace of the error from the device while you're working in a Windows environment.

The device logs would hold the exact cause for the error - usually when the app crashes, the root cause lies somewhere in the native code and the AppBuilder DevTools cannot get that exception as they close with the app. You can get the device logs on a Windows machine once you sync your device through iTunes - this article describes that option in more details. However, since Apple symbolicates the iPhones crash reports, outside xCode it's hard to get to the stack trace of the error.

You can try narrowing down the piece of code leading to the crash by removing parts of it until you get to the exact line that crashes the app. As long as your app is running, the AppBuilder DevTools should also run and you should be able to debug the app - hopefully you will be able to get down to the exact error that way. 

Regards,
Tina Stancheva
Telerik