- This topic has 3 replies, 3 voices, and was last updated 9 years, 1 month ago by
.
-
Posts
-
Downloaded and installed the latest version today only to find it requires Android 4.4.4 and my latest device is 5 months old and running 4.2.2.
What? You want everyone to upgrade devices every time you have a new build? Seriously!
Android 4.4 is the first version of android that supports remote debugging. GapDebug makes use of this capability.
If you’re device is not at the Android 4.4 level consider giving genymotion (https://www.genymotion.com/) android emulator a try. Its a much better experience than the Google Android emulator. I use it frequently to test for devices/os versions that I don’t have a device for, e.g., lollipop.
Downloaded and installed the latest version today only to find it requires Android 4.4.4 and my latest device is 5 months old and running 4.2.2.
What? You want everyone to upgrade devices every time you have a new build? Seriously!
>What? You want everyone to upgrade devices every time you have a new build? Seriously!
Please note that GapDebug has never supported debugging android apps before Android 4.4. The requirement has been in place since the very first GapDebug beta. The background for this requirement is that before Android 4.4 there was no internal api for us to be able to access for debugging info. Some good news coming soon for development on and debugging pre-Android 4.4 devices is the Crosswalk webview container as a backward compatible rendering engine based on the latest version of Chrome (chromium to be more accurate). GapDebug supports debugging apps that use the crosswalk webview.
