The target device must have USB debugging enabled. Edit that file (if necessary) and return here, or continue now and edit the file later.
A target device running Android 4.4 (KitKat) or laterīefore continuing, check that the tag in the app's Config.xml contains a value of "1" (see the Config.xml Reference for details). Chrome 32 or later installed (Chrome Canary recommended). Mac OS X or Windows development host with ADB installed. It includes live screencasting from the remote unit to the development host, and supports port forwarding and virtual host mapping in case your device needs to access a development server. Google Remote Debugging works with native Android apps that use WebView as well as purely browser-based apps. If you're building an Android app and have a device with Android KitKat 4.4 or higher, Google Remote Debugging is an alternative to Weinre that's a bit easier to install and offers some great visuals for testing, debugging and fine-tuning your app while it's running on the device. A WebView-based app configured for debugging. A USB cable for connecting the target to the dev. 
A Zebra target device (Android or Windows Mobile/CE). Chrome 32 or later (Chrome Canary recommended). Android Debug Bridge ( ADB) or MS Mobile Device Center (or ActiveSync). Platform-specific requirements, if any, will be listed in the section that describes the individual debugging tool and/or method. General requirement guidelines are listed below. Requirements of the development host vary based on the target device and its OS platform. Remote Debug Inspector - works with Windows Mobile/CE devices that use the Zebra Webkit. Weinre - is a node.js application that can effectively test most apps running on Android Jelly Bean as well as Windows Mobile/CE devices. This guide includes instructions for enabling debugging on an Android device and describes three methods of debugging Enterprise Browser apps while they're running on a device:Ĭhrome's Web Inspector - works with Android KitKat and higher, is easy to set up, and offers screenshots and other nice extras. 
Although much can be accomplished using emulators and an IDE, applications often behave differently when running on hardware, and features such as Barcode scanning are impossible to test without the use of physical hardware to perform the scan and acquire the data. Just as debugging should be thought of as a vital part of every development cycle, on-device debugging should be part of any effective testing regimen.
0 kommentar(er)
