- This topic has 10 replies, 2 voices, and was last updated 8 years, 4 months ago by support-michael.
-
AuthorPosts
-
nsicardParticipanted.support_michael, marking FIXED.
See the new GapDebug 2016 update-2 (2.4.0) release that includes a fix for this issue.Hello!
I’ve used Gap Debug for some time and works wonders! But just now there’s something going on, and it’s not working in a strange way.
0) version of GapDebug installed: GapDebug Version 2016 Update (2.3.0)
1) Mobile device and OS version: I am currently using an Android ADV with Android 6.0
2) Workstation OS version: Mac OS X El Capitan 10.11.5
3) Description of the problem and if you can reproduce it consistently: It has happened every time, It looks like it detects the ADV and shows the app I am running, but doesn’t show anything on screen.
4) screenshot: http://imgur.com/l0Sq4kV
Hope this is enough information.
Thanks!
Attachments:
You must be logged in to view attached files.
support-michaelKeymasterThanks for good report and including the console log info in the screenshot. The issue for the white screen is that GapDebug downloaded an older version of the Chrome Dev Tools (CDT) from Google for the device. I’m working on understanding the root cause. Please try the workaround described in this post: https://www.genuitec.com/forums/topic/android-debug-whitescreen-workaround/
Let me know if the workaround clears up the issue for you.
nsicardParticipantHello!
Thank you for the quick response. I did all that said in the workaround, and it looked good until the very last step. It did start updating something, it said on the screen. But after that the screen remained blank. Here I attach a screenshot.
I understand you are working on having this fixed.
Thank you!
Attachments:
You must be logged in to view attached files.
support-michaelKeymasterThanks for giving the workaround a go. The issue is that GapDebug is requesting an incompatible version of Chrome Dev Tools from google for your device. As the console log expresses the version Google returns includes the obsolete and unsupported Object.observe() function. Why this happens for some versions of android/device combo and not for others is unclear to me. I’m still digging into this and hope to have a resolution very soon. I’ll update this thread once I have more info.
support-michaelKeymasterUpdate: we have a fix that we are integrating now. I’ll update you on when we will ship an update (we will do it as quickly as possible).
nsicardParticipantAwesome! Thank you for the follow up.
support-michaelKeymastered. michael – updated download links; replaced dropbox download links.
@nsicard
I have a GapDebug test build that I’ve created with a fix for the issue you reported (i.e., Object.observe function). Would you please install and verify that the fix works with the ADV that GapDebug was breaking on? Once we have completed testing I’ll roll out the production version. Let me know your results asap.windows:
https://drive.google.com/open?id=0B2UbQ9Htq1UWTHlwa2lqVVJzMHcmac OSX:
https://drive.google.com/open?id=0B2UbQ9Htq1UWRUQ2NlJkYnpsTzQ
nsicardParticipantHello,
I’ve tried to get the update, but:
“This account’s links are generating too much traffic and have been temporarily disabled!”
(I’m clicking on the Mac file)Thank you!
support-michaelKeymaster@nsicard
See the new download links. I updated the download links in the post above your’s.
https://www.genuitec.com/forums/topic/gapdebug-not-showing-anything/#post-490226
nsicardParticipantIt does work!
Thank you very much 🙂
(Sorry about my confusion about those links)
Outstanding support here!
support-michaelKeymaster@nsicard
Thx for the help in resolving this issue. I’m moving forward prep’n a release and will give you a ref in the relnotes & @GapDebug. Tagging this thread closed. -
AuthorPosts