Guys how to overcome from this problem while launching the iOS app from appium server, unable to open appium inspecter
please help me out to come out of the group guys.
this below warning message from in the pop up
Be sure the Appium server is running with an application opened by using the "App Path" parameter in Appium.app (along with package and activity for Android) or by connecting with selenium client and supplying this in the desired capabilities object.
please help me out to come out of the group guys.
Build the app through XCode, and then specify path to the app, you should be able to find it through XCode.
Update
I had the same problem a while, here is how I solved it:
Build the application on your Mac using Xcode Simulator
Find location of the app on your machine, here is how to do it
Enter the path in Appium GUI
Now you should be able launch inspector
Some additional information:
My old blog on how to setup Appium GUI
Blog on how to start using Appium tutsplus
Appnium can only recognized .app file. It cannot open the .ipa file.
Related
I'm trying to test my Xamarin.Forms app with Xamarin.UITest. Android works fine, but the iOS part has problems. When executing my first test to get into REPL I get the following error:
SetUp : System.Exception : Unable to contact test backend running in app. A common cause is that the app is not properly linked with Calabash. Please verify that it includes the Calabash component.
The strange thing is, when uploading the app to the Microsoft App Center it starts a test. It just hangs because it fails to find my toolbaritems. I wanted to check for a valid query with REPL by doing the iOS test on my Mac, while I'm usually working on Visual Studio on Windows.
I tried the solutions I found online with no luck
My .iOS project includes the Xamarin.TestCloud.Agent
In the AppDelegate.cs I have Xamarin.Calabash.Start() directly after global::Xamarin.Forms.Forms.Init().
I have NUnit 2.6.4 and NUnitTestAdapter 2.1.1 in the UITest project
I am using my Debug/IPhoneSimulator configuration
I am compiling an .app file from Visual Studio on Windows connected to a Mac and start the iOS test on the Mac.
This is my current code for the AppInitializer:
return ConfigureApp.iOS.AppBundle(sPathToiOS).PreferIdeSettings().StartApp();
Sometimes I also get a different error:
SetUp : Xamarin.UITest.XDB.Exceptions.DeviceAgentException : Unable to contact DeviceAgent
----> System.AggregateException : One or more errors occurred.
----> Xamarin.UITest.XDB.Exceptions.DeviceAgentException : Unable to contact DeviceAgent on 127.0.0.1
----> System.Net.Http.HttpRequestException : An error occurred while sending the request
----> System.Net.WebException : Error: ConnectFailure (Connection refused)
----> System.Net.Sockets.SocketException : Connection refused
This seems to be happening when the simulator is not running when starting the test and it takes to long to start the simulator.
I had to make sure I had re-deployed the app onto the simulator I am going to test on, with all the necessary steps in place.
What happened to me specifically is that I added the Xamarin.Calabash.Start() to the AppDelegate.cs file, but I had to make sure to redeploy to the simulator (by just starting the app in debug mode in my case), exiting out, then starting up the UI test(s).
This will ensure that the correct version of the app is on the simulator. This is the only way to test on the simulator; it won't deploy the app for you before running the tests.
So if someone has a similar problem like me and comes into this question: My solution is to connect a physical device to the the Mac and run my UI-Test on it. Keep in mind that you have to activate UIAutomation in the developersettings on the device. Now I can run my tests with no problem.
In my case, Calabash was not included in the build of my Xamarin.iOS solution when running my Xamarin.UITest.
I've fixed my problem by following this documentation :
adding Xamarin.TestCloud.Agent in the Xamarin.iOS project
launch Xamarin.Calabash.Start() in AppDelegate.cs file
In my case Xamarin.Calabash.Start() was under a preprocessor directive (#if TEST) that was not executed. Just make sure the directive is in place to solve the issue
Unable to inspect element from appium inspector for android device on Mac PC.
Mac: 10.13
Appium: 1.7.2
Appium Inspector : 1.5.3
Android Device Simulator: Pixel-2
Android Version: 8.0
I am able to inspect element for iOS (iPhone device) for the same application, but unable to inspect the element in android.
When I click on inspect icon of appium dmg of 1.5.3 (in Terminal i run appium 1.7.2), it launches the device but i dont see anything in appium inspector tool.
Please help, I have tried UIAutomateviewer as well, but since my application dont have most the ID's for most of the elements so I need XPATH in my script.
I may be wrong but trying to help:
Try uiautomatorviewer if your application does not have id then certainly can use resource-id as id
Or can use XCUI test
Very well explained here:
http://developers.perfectomobile.com/display/TT/Finding+Elements+on+XCUITest+devices?src=contextnavpagetreemode
Also, this webpage explain how to fetch xpath
https://bitbar.com/appium-tip-13-use-inspector-or-uiautomatorviewer-for-ui-element-inspection/
XCUI explained in detail
https://github.com/appium/appium-desktop
https://www.youtube.com/watch?v=4BgkVp0v3BM
Also can try Macaca inspector if you have not tried before, this worked for me with appium 1.6
https://gopekannan.wordpress.com/2017/02/03/macaca-inspector-for-apple-mac/
Thanks
Abhishek
first of all you need to set the desired capabilities in the new session window for inspecting elements of the android app.
the three imp DC's are -
1. app -> add the path of .apk file
2. deviceName-> to get the device name, type adb devices in terminal and get the device name from there
3. PlatformName -> android
start the session.
soon you will be able to inspect the elements.
If your facing any issues, let me know i'll be happy to help.
I have resolved this issue by downgrading my Android version to 6.0.
However please let me know if any one of you have solution for the latest android versions
I am using appium version 1.3.7 version.
After starting appium sever, the app get installed in ios simulator.
When I tried to inspect using appium inspector, the refresh button in the appium inspector keeps on loading, it doesn't load the home page of an app at all.
I think you need to update your appium, since new appium version support XCUITest you might be ended to some changes in locators and other setup. This is my suggestion because you need to automate your cases on iOS 10, so in that cases you forced to upgrade the appium.
Coming to your question, if you are not able to access the appium inspector there is workaround.
How to inspect ios elements ,
Option one : https://www.youtube.com/watch?v=254nbRjjQjc
Option two : https://www.youtube.com/watch?v=4BgkVp0v3BM
For more videos :
https://www.youtube.com/channel/UCaJA59vxBDS7smS81Gqf7KA
Are you using Windows or Mac machine? I would suggest to use ~/android-sdk/tools/uiautomatorviewer. This will open one window, you can take screenshot of current screen from connected device and from left pane elements can be inspected.
I have installed Blackberry on Windows7. I got all three .csi files from BB. I have done all the procedures and got a successful response from there. Then i right clicked my project and clicked on "sign with signature tool". After signing i loaded this project on Blackberry Bold Device.
Now My Device Shows the installed icon on screen but when i try to open this project it says that "attempts to access a secure api." how to resolve this problem.
For resolving this problem i have also Disabled my UAC. I am working on eclipse Helios.I installed Blackberry Plugin with this exe file. "BlackBerry_JDE_PluginFull_1.5.0_helios" is there a problem with this setup.
I am not able to launch a simple helloworld application on Device. I have tried all the help from internet but still i have not succeeded. plz help to resolve this critical issue.
You need to sign your application. Contact RIM for signing keys. Install them and sign your app before installing on actual device.
Check this link to obtain signing keys: https://www.blackberry.com/SignedKeys/
How to Run two instance of BlackBerry simulator in windows eclipse?
The documentation regarding developing with BlackBerry Messenger indicates that you can run two simulators at once, at least with the simulators that come bundled with the BBM SDK.
You cannot. If you try, you will get an error message saying only one simulator can run at a time.
What you need to do is:
Install the blackberry eclipse plugins twice and make two
workspace of each eclipse.
Run the two simulators in each eclipse and error like "could not
open port 19780 and it is use by another program....." will pop
out in one of your simulator.
So made the changes in pin,
data-port values in .bat files, rimpublic.property files inside
MDS and fledge-settings.conf in one of your simulator... but this
changes will not be reflected on your eclipse.
So what you need to do is, when you click the debug configuration from your
eclipse, you will see the simulator option there. So, click the simulator and change the PIN value, whatever you have made the changes in .bat files.. and just after that in the simulator you will again find the option of network, there unselect the disable registration button...once all this changes is made click apply and restart your eclipse... this will surely solved your problem