I have installed appium version 1.3.3.
I have launched appium server to inspect an ios app.
I have attached the screen shot for reference.
I am getting the below mentioned error message.
Try getting the test app on your simulator with the Xcode, and then running Appium inspector. It would eliminate if issue was caused due to Instrument not being able to communicate with device
Related
Xcode 9.2 debugging on an iOS Simulator has completely broken for me.
I worked on this for hours and tried a ton of suggestions short of completely wiping my hard drive and starting out with a fresh operating system install. I ended up filing a bug with Apple. Posting here in case anyone has encountered this problem and has any suggestions.
Summary:
When try to build and run in debug mode with a debug executable. The simulator only opens the application to a white screen and then Xcode pops up an error:
Could not attach to pid: "<a process id>"
Ensure "<app>" is not already running, and "<user>" has permission to debug it.
Steps to Reproduce:
Make any project and try to run on any simulator.
Expected Results:
Debugger successfully attaches to debugger.
Actual Results:
Debugger is never able to attach to the iOS simulator process/app for debugging.
Debugger CAN attach and build and run successfully on a physical device.
Version/Build:
- Xcode Version 9.2 (9C40b)
- macOS Sierra 10.12.6
- Any iOS project
- Any iOS simulator
Other notes:
- Xcode 9.2 was working fine until this problem randomly started. The error initially said:
Failed to initiate service connection to simulator
DTServiceHubClient failed to bless service hub for
simulator iPhone 8 Plus <simulator identifier>
- After rebooting computer, the error shifted to "Could not attached to pid..."
I tried dozens of suggested solutions short of completely wiping my computer including:
Resetting device contents and settings on simulators
Create a new device (even different device and OS combinations)
Try different Xcode projects, even simple one-off single view applications
Looking at the etc/hosts file and verifying localhost can be pinged
Restarting computer multiple times
Deleting out derived data (multiple times)
Let it build and run without attaching debugger, then try to attach debugger by "attach to process id"
Completely uninstalling Xcode and all simulators, and reinstalling.
Removing any invalid certificates in keychain
It turns out our security software was blocking the debugger. Running sudo sysdiagnose helped me find a log entry showing that it was being blocked. The software is Cb Defense (Carbon Black Defense). Apparently the only workaround is for your security team to whitelist by a hash, and that hash could change in the future.
There is a bug in Xcode 9.0-9.2 that causes this issue to appear after running for a while. If you log out and back in it should resolve it for you.
I am getting below error in appium inspector when I try to open appium inspector:
[sessionCapabilities()] Error response status: 6, Selenium error:
Session does not exist
Please note that my automation code is running successfully. I am trying to launch inspector while the script is running.I am using the same session id which is automatically generated in inspector while script is running.
I am using appium 1.2.3 desktop with server 1.7.1,Xcode-9,iOS-11,IPhone 7 Plus real device.
Can anyone help me on this?
try this out .. hopefully it may solve your problem
https://github.com/appium/appium-desktop/issues/308
I am unbale to get the logs for ios simulator.
I tried with finding the folder core simulator but unable to do
You can start the appium with option :
appium --show-ios-log
Hope that one helps. Thank you
I have installed appium Version 1.4.13 (Draco).
In the appium iOS configuration provided the following details
a. app path /Users/mac/Documents/testing/automationTesting.app
b. Force device iphone6,
3. platform version 8.2
4. unchecked the UDID and bundle ID. The .app was generated using Xcode ver 7.0.1
After launching the appium and getting the response code 200, i tried to launch the inspector and it gets launched successfully.
I see the below debug info on the appium console
info: [debug] Responding to client with success: {"status":0,"value":{"build":{"version":"1.4.13","revision":"c75d8adcb66a75818a542fe1891a34260c21f76a"}}}
info: <-- GET /wd/hub/status 200 1.036 ms - 105 {"status":0,"value":{"build":{"version":"1.4.13","revision":"c75d8adcb66a75818a542fe1891a34260c21f76a"}}}
Where as no images are getting loaded in the inspector and also the iOS simulator which was running before gets disappeared.
I have also looked into the below stack over flow urls and ensured that the steps are followed
Appium Inspector not able to load image
appium inspector not running on mac
Any inputs/suggestions would be of help
Option 1:
Instead of simulator i tried to configure the appium to run on the device by providing the UDID and bundle ID. I was able to launch the inspector successfully and get the UI elements values required for automation.
Option 2: I had upgraded the xcode to the latest version and it started launching the inspector in the simulator mode itself.
Am trying to run appium tool for testing apps. While starting appium server i finished all setting right way. When appium running the app will start at time but suddently it get crash.
Yes.Am using Xcode 6.0 and Appium 1.3.4
Make sure the .app file you are using is build for simulator if you are running appium for simulator and a different build i.e the build for device if you want to run it into real device....This is one of the cause which causes the instruments to crash at start up.
When I create an new project with XCode then generate the app file, it is working fine - I can open the inspector.
But I have a problem when I use an already developed application and the build is coming from a developer profile : I can't open the inspector and instruments crash on startup.
While running the script please start xcode and go in the settings of the mobile device and find developer options. Make sure UIAutomation is enabled there. If it is not then enable it and after it try to run the script again. Surely it will work.