I have an issue with the web app client running in the browser on Windows 7. Unfortunately, some clients still use Windows 7. The app runs on the browser, but all buttons are disabled. It is the same issue with Chrome and Firefox which are updated. Do you have any idea how to fix this?
Thanks for any help!
Related
I am using eclipse, Appium 1.6.4 and Android Studion with Android 7.0 also tried with 6.0.
I run my automated test and it executes, it connects to the device, it opens the chrome browser but then doesnt navigate to the google url using the driver.get(...) method it just says data;, . I dont get any errors until it eventually times out and tries running it again.
Any help would be appreciated as ive tried a few things and got nothing.
Thank you.
I have Samsung device with stock browser that called Internet.
The device is over 4.4 version.
I'm trying to remote debug the stock browser on a real device without success.
Already succeeded to remote debug chrome.
Is it possible on a real device and not on emulator?
The problem is just Samsung's stock browser
Hi!, Appium started to work with Android's stock browser (named.. Browser) since v1.3, the actual problem is the Samsung stock browser isn't Browser, it's Internet! These both apps are different (shame on Samsung!, not Appium guys fault). All other Android distributions that stock browser is Browser are working fine with Appium >= v1.3 as I've said before.
Emulator stock browser is Browser, that's why it's working for you on Emulator!
Why Appium doesn't work with Samsung's stock browser?
Appium are built to work with Chromium WebView (present on Chrome and Browser) , and Internet does not have it. So it doesn't work with Appium now, and probably won't work never, as Appium's maintainers does not have any interest to do the automation outside Chromium WebView. See this issue for more information: https://github.com/appium/appium/issues/4509
Ok, but how do I use Appium with Samsung devices?
So, the only solution is installing Chrome into your samsung device.
If you can't access the store to install the Chrome app, you can download and install manually the Chrome APK into your device (or other browser that uses Chromium webview, such as Chromium and ContentShell).
PS: ContentShell is basically only Chromium webview, without favorites, bookmarks and other common browser stuff, so it's pretty good for Appium testing.
I need to troubleshoot an issue happening in a webview running within my app. This issue only occurs on Android versions lower or equal to 4.3. My app requires an up to date version of Google Play services.
In order to troubleshoot my webview, I usually can run my app under the Android Emulator (with the latest version of Android), then connect to the web view via Chrome (using chrome://inspect) - the web view appears in Chrome and I'm able to browse the DOM and debug.
To run the app under 4.3, I've created (under AVD) a new device from an existing device definition,
then picked the target Google APIs (Google Inc.) - API Level 18. I've then installed my app, but when trying to run it, I get the error message "This app won't run unless you update Google Play services.". There's an "Update" button on the previous dialog, but nothing happen when clicking on it.
I then tried to debug my issue using Genymotion. I've created a device under 4.3, followed these instructions to flash my device with the latest Google Play services and installed my app. I can now run the app and reproduce the issue within this simulated environment.
The trick now is to be able to connect to the web view from my local Chrome browser. I've enabled remote debugging as described here. Now my device appears in Chrome, but the web view is not showing up in the inspector. Similarly, if I open a new tab under the native browser, it won't show up in the remote inspector. If I open a new tab under Android Chrome though, I can see it showing up under my remote Chrome inspector.
I can see two way moving forward and successfully accessing to the DOM of my webview:
Fixing the "Update" issue under the Android Emulator running 4.3
Or
Connecting to my web view from my Chrome inspector while running the app under Genymotion
Any idea on how to solve one of these two problems?
I have been using weinre for sometimes. it's a pretty good tool to debug webview for android 4.3 and lower. It provides almost same interface as chrome debugger.
All you need to do are:
Install weinre
sudo npm -g install weinre
Client side:
Insert the following code to your webpage <head> section.
Note: it's better to put it at end of <head> section, otherwise there will be some strange errors and debugger won't show up.
<script src="http://<your server ip here>:8081/target/target-script-min.js"></script>
Server side
weinre --boundHost -all- --httpPort 8081
Debugger
open the debugger tool from weinre from your desktop browser:
http://localhost:8081/client/
Finally,
select any target in Targets part and then start debugging.
Remote debugging web views only works on devices with android 4.4 and above.
have a look at this :
https://developer.chrome.com/devtools/docs/remote-debugging
I have been working on a browser plugin for windows which involves displaying camera output in browser. Presently I'm working on Windows 7. After plugin installation, I want to start the plugin immediately without restarting the browser. I noticed that as soon as plugin is registered, it started working in Google Chrome Version 24.0.1312 as well as in Internet Explorer 9. But it fails to do so in Mozilla Firefox 18.0.1. Can anyone help me solve this problem of restarting the browser after plugin installation. And will this problem occur in MacOS as well?
Thanks
You need to do a navigator.plugins.refresh(false); in javascript to tell the browser to rescan the plugins.
Explore /Installer/js -folder in FireBreath sources
I am using Windows XP SP2 and Chrome (version 9.0.597.19) but every time I run gwt in developer mode I see:
"Development Mode requires the Google Web Toolkit Developer Plugin..."
No matter how many times I install it.
How can it be that gwt developer mode is not running in google's own chrome in xp sp2?? This is outrageous??!! It is working in FF but is very slow.
Do you have Click-to-activate-plugins enabled in Chrome? I had, and I had to click on the little puzzle piece in the URL-bar and select that all plugins may run on 127.0.0.1.
Google Web Toolkit plugin is for Firefox 3.5.x and 3.6.x and
probably Google Chrome 7. I'm also using Chrome (version 9.0.597.19) which doesn't support GWT plugin
I was having this same problem. Every time I clicked "Download the GWT Developer Plugin
For Chrome" it would start to load and then just stop without anything happening. Eventually I opened the link in a new tab and got a captcha with this message:
"Our systems have detected unusual traffic from your computer network. This page checks to see if it's really you sending the requests, and not a robot."
Maybe you are having the same problem?