This thread was migrated from an old forum. It may contain information that are no longer valid. For further assistance, please post a new question or open a support ticket from the Customer Support portal.
I am trying to debug my application following this tutorial.
I'm using Visualizer Enterprise V8 SP 1 FP 13 installed on Win 10 Enterprise V 1709 OS Build 16299.125 and phone Huawei Mate 10 Lite Android 7.0 with Mobile Visualizer app V 8.1.0
The steps I'm doing as follows:
I'm opening Visualizer app on my phone
I'm connecting my phone with an USB cable
Going to local preview and the name of my app is cached from previous local runs
Clicking on Product -> Debug as -> Debug Android application
I'm getting broken blank Chrome screen (p.6) and nothing happens, when I click Connect on my app I'm getting error message : "Perform Preview-Run and try again". When I do that nothing happens....
This is know issue with latest version of chrome, you need to downgrade the chrome version to debug the application. Please check the below post for more information.
Hello @Twvcey Rvndvll I will try tomorrow with your suggestion to downgrade my browser. But i'm not sure I want to do that.. When will be provided a fix regarding that issue ?
I am not able to open the link you refer to. I got 404 error.
If the chrome downgrade allow me to debug the app I will mark your answer as best, but I need to know the deadline for the fix. I suppose it's planned already. Since I don't won't keep my chrome older version.
Just to clarify:
My version is Chrome 65.0.3325.181 (Official Build) (64-bit) (cohort: Stable) released on 2018-03-06
Will it work with Chrome 64.0.3282 released officially on 2018-01-24
I have already installed Java SE SDK and Android SDK but I have the Android studio as well since i needed emulator. I see in the attachment with !! not to install it. Is it a problem?
I understand that.. I watched the attachment of @Twvcey Rvndvll which is way more detailed but the problem as I wrote in my comment is that I have installed Android Studio. Please check page 1 point 2 from @Twvcey Rvndvll ' s attachment. Thanks!
This Chrome version 62 or is released 5 months ago. How could you didn't manage to fix that issue?. I don't want to do the things described in the document. In my answer to Shaik, I asked when a fix will be provided and whether this is planned? I won't delete chrome_update.exe or touch it's registry keys with that workaround sorry. Thanks for the quick responses although :)
Wanted to provide you an update that this issue has been fixed and we will be releasing this as part of Kony V8 Service Pack 2. This release is going GA by end of April 2018.