I am inspecting a screen on iOS app but it doesn't provide any elements on that screen.
Appium inspector is not providing any objects on that screen. Please help .I am stuck here.If any other way to inspect the iOS screen please suggest.
I am using Appium Desktop v1.9.0 in mac
https://i.stack.imgur.com/HZVkf.png
In this case you do following things...
Ask your IOS developer to give specific id for the outer container to inner container if present.
If you have id for the container and if you are not getting for specific element then ask your developer to add id to that element.
And take a fresh new .app build and then recheck and hope your problem will be solved.
Related
appium logs 2nd part
appium logs first part
UI Automator showing element properties
UI Automator showing all element properties
Summary:
Appium is unable to identify any element on particular page of My Mobile native app. I have used all the possible locators for different elements shown on that page with help of UI Automate Viewer.
Used different locators (by id/xpath/contains/accessibility/UIAutomate).
Verified that the page belongs to native app only with no Web View.
applied different types of sufficient wait for the page.
driver.get.pagesource not working for the page.
Can any one please help in same, the below ways I have opted for finding the solutions but nothing has worked till now.
You say a native apps, but seen from the picture, that you facing with like a Maps application (this is web apps, my assumse), often in testing things like this happen, like you have to do a switch context. When you are on this page please try this :
driver.context("WEBVIEW_1");
And this is for switch again to native :
driver.context("NATIVE_APP");
Please read this reference and this.
I am automating a native android application using appium and java. I could find locators of each element. Please refer below screen shots for your reference. Its not working as expected and getting me time out exception i.e. failed to find element where you can see, I have given correct id.
For time being, I am using touchaction with x,y co-ordinates which is not correct solution. please help me to solve it.
Code snippet:
For example :
Exception Screen shot:
Try invoking driver.getPageSource() method and double check that the desired element is present in the XML page representation.
Going forward you can set printPageSourceOnFindFailure to true so Appium would print the source code of the page to the STDOUT on element find failure like:
caps.setCapability("printPageSourceOnFindFailure", true);
More information:
Appium Desired Capabilities
Appium Studio for Eclipse - Capabilities Manager
I started exploring react-native. One thing which I want is should able to debug my app from chrome. I am having prior experience to cordova. Cordova renders app in chrome web view. I understand that with react-native it is not possible because react-native doesn't render app on web view.
There is an option react-native "debug in chrome". When I click this option, attached screenshot is getting opened. I enabled "pause on exception."
But nothing is happening. I am unable to see my app code at all.
I like to do step by step debugging. Is it possible? If so can some one tell how to do this?
You can definitely examine the source code, set breakpoints, etc in Chrome.
In the Sources menu, select debuggerWorker.js and then you should be able to see your project tree.
Any console.log in your code will print to the browser too. But I find the breakpoint inspection most helpful.
this is simple as you were doing in cordova.
try to put debugger; statement in your code while in debug mode.
It will set the breakpoint and you can then debug your application. No need to find out your files in debuggerWorker.js
I have created one ionic app it runs perfectly fine in browser but when I convert it into app it gives white screen.
I have already install white list plugin and allowed all url in config and also have kept meta tag. Am not able to find any other solution.
When kept simple html file am able to view it.
Any help will be grateful.May be good way to debug will be also good.
Connect your phone to PC with USB cable and remember to keep USB Debugging On. Now, navigate to chrome://inspect. You'll find the device name and click on "inspect". On Console tab, the error list will give you a hint about what is wrong there.
In my case, a custom service was Injected in controller which had been removed at some time as It was not used anywhere.
Ok just answering this question so it will be helpful to all.
Below blog was helpful for me that how I can debug
http://gonehybrid.com/how-to-debug-the-white-screen-of-death-in-your-ionic-app/
And guess what was issue, folder name in app is case sensitive. I was just need to change a folder name as per exact case sensitive path I provide in index file.
Mostly such thing occures because of a javascript error. You say it runs in your browser. Are there some exception in the console?
Not everythings is equal between browser and device, for example plugins. You have to be sure, that all used plugins are installed properly.
If you deploy on android, you can use android monitor to get console output. On ios xcode has already an integrated debugger.
I had this horrible issue because I compiled my Android application with Cordova 6.x and the project worked with CrossWalk plugin. In my case, the solution was uninstalling Crosswalk. If your project has installed that plugin, try to uninstall it and compile your project again.
I'm having an odd issue after having migrated my drupal project to a client's server.
After configuring the apache http.conf to accept clean urls, I'm now finding that the administrative overlay does not always respond.
-The Find content shortcut doesn't respond, but the Content link on the overlay does.
-The Edit link when on a node's detail page makes the site darken like it does when the overlay is being loaded, but the Edit window for the node never appears.
-The X (close) on an overlay page (like when using Content to see the list of all nodes, but then want to quit out of it and go back to the site) fails to close the overlay and a strange, second vertical scrollbar appears on the right of the browser screen.
I have had a similar problem before, but chalked it up to javascript on the page interfering with the overlay's own javascript. Now I'm not so sure.
If anyone else has had this problem, or can surmise what the issue might be, then I would appreciate any and all help given.
My thanks,
~M#
It looks as if you are using a jQuery version that is incompatible with the overlay module. It's probably because $.browser is deprecated in jQuery 1.9, see the following issue:
Uncaught TypeError: Cannot read property 'msie' of undefined - jQuery tools
To fix this issue, you'll need to install the latest jQuery Update module and select something below jQuery 1.9 for the admin interface. This should clear up your problems in IE.