Appium 1.4.13 Released

News
21

Hi Vpathania,
I followed Sruthi instructions with two additional steps and I got it to work.
I added the code-signing identity and it worked for me.
I was able to install appium 1.4.13 without error. See if it will work for you too.

  1. Type in terminal git clone https://github.com/appium/appium.git

  2. Type in terminal to find code-signing identity:
    security find-identity -v -p codesigning

  3. Type in terminal $ ./reset.sh --ios --real-safari --code-sign ‘code signing identity’ --profile ‘retrieved profile identity code’

Check out instructions here
https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/mobile-web.md#mobile-safari-on-a-real-ios-device

22

Awesome ,

thanks Guys working for me now…

info: [debug] Responding to client with success: {“status”:0,“value”:{“build”:{“version”:“1.4.13”,“revision”:“88e67ce987d78ce44de252219e07dc176a3511c2”}}}

23

++ Thanks seleniumappiumnewbie, For me also it is working in My Machine too (Appium 1.4.13)… :smile:
but iOS 9.0 version is not displayed in Appium GUI, because of older version of XCODE(6.2) i have. so trying to update my MAC OS X which is compatible with XCODE 7 version.

24

Hi Sruthi and Seleniumappiumnewbie,

I have updated to Appium 1.4.13 successfully, also upgraded my mac to the El Capitan new OS version 10.11 and Xcode to 7.0.1…

  1. After Xcode upgrade to 7.0.1 all the simulators iOS version 9.0…
  2. But when i trying to update in APPIUM GUI the platform showing till 8.4… not showing the 9.0 Version…when start the appium server by keeping 9.0 Version forcefully then app is getting crashed…
    Screen Shot 2015-10-08 at 11.16.48 AM.png1370×1098 251 KB

    below is the error, which is displayed on appium logs…

info: [debug] Attempting to run app on iPhone 6 (9.0) [

info: On xcode 7.0, instruments-without-delay does not work, skippinginstruments-without-delay
info: [debug] Spawning instruments with command: /Applications/Xcode.app/Contents/Developer/usr/bin/instruments -t /Applications/Xcode.app/Contents/Applications/Instruments.app/Contents/PlugIns/AutomationInstrument.xrplugin/Contents/Resources/Automation.tracetemplate -D /tmp/appium-instruments/instrumentscli0.trace -w “iPhone 6 (9.0) [” /var/folders/6y/3w4t1jld3997y9q_6cvwswqr0000gn/T/11598-5518-63ryqs/Payload/TheWeather.app -e UIASCRIPT “/Users/monocept/Library/Application Support/appium/bootstrap/bootstrap-e16e825cd345231b.js” -e UIARESULTSPATH /tmp/appium-instruments
info: [debug] And launch timeouts (in ms): {“global”:90000}

info: [debug] [INST STDERR] 2015-10-08 11:00:21.499 instruments[5622:274330] WebKit Threading Violation - initial use of WebKit from a secondary thread.

Please help me out here … :smile:

25

I manually typed in 9.0 in the platform version. Click between screens to make sure it remembers 9.0 version you entered. Then relaunch appium. See if it works for you.

26

++ Seleniumappiumnewbie

I kept forcefully 9.0 and did what u suggested and ran the appium but still app getting crashed…

info: [debug] [INST STDERR] 2015-10-08 11:22:03.263 instruments[5811:288398] Attempting to change event horizon while disengage
info: [debug] [INST STDERR] Instruments Trace Error : Target failed to run: The operation couldn’t be completed. (FBSOpenApplicationErrorDomain error 1.) : Failed to launch process with bundle identifier ‘com.weather.TWC’
2015-10-08 11:22:03.264 instruments[5811:289237] Attempting to change event horizon while disengage

info: [debug] [INSTSERVER] Instruments exited with code 253
info: [debug] Killall instruments

info: [debug] Instruments crashed on startup
info: [debug] Attempting to retry launching instruments, this is retry #1
info: [debug] Killall Simulator

27

Sorry, I don’t know. I’m new myself. Maybe Sruthi or someone else can help.

28

I also run this in my terminal when after I start the appium server with the real iPhone device connected ./bin/ios-webkit-debug-proxy-launcher.js -c xxxxyouruuidnumberxxx:27753 -d

Not sure if you already have done that.

29

I am running in simulator though i tried that command but showing as No such file or directory error.

ravis-MacBook-Pro:~ monocept$ ./bin/ios-webkit-debug-proxy-launcher.js -c xxxxyouruuidnumberxxx:27753 -d
-bash: ./bin/ios-webkit-debug-proxy-launcher.js: No such file or directory
ravis-MacBook-Pro:~ monocept$

Im able to run my script in iPod device with ios 8.4, only prob with Simulator.

30

The simulator doesn’t need the iso-webkit-debug-proxy-launcher then only the real device does.
I am also stuck on the simulator issue. I’m staying up late trying to figure it out. My iPhone real device works too, but just not the simulator. Sorry I’m stuck too.

I get this error.
A new session could not be created. (Original error: Failed getting devices. Err: Error: Command failed: /bin/sh -c ‘/Applications/Xcode.app/Contents/Developer/usr/bin/instruments’ -s devices
. Stdout: . Stderr: .) (WARNING: The server did not provide any stacktrace information)

info: Welcome to Appium v1.4.13 (REV 88e67ce987d78ce44de252219e07dc176a3511c2)

info: Appium REST http interface listener started on 0.0.0.0:4723

info: [debug] Non-default server args: {“safari”:true,“deviceName”:“iPhone 6”,“platformName”:“iOS”,“platformVersion”:“9.0”,“browserName”:“Safari”,“showIOSLog”:true,“defaultCommandTimeout”:7200,“debugLogSpacing”:true}

info: Console LogLevel: debug

info: --> GET /wd/hub/status {}

info: [debug] Responding to client with success: {“status”:0,“value”:{“build”:{“version”:“1.4.13”,“revision”:“88e67ce987d78ce44de252219e07dc176a3511c2”}}}

info: <-- GET /wd/hub/status 200 12.620 ms - 105 {“status”:0,“value”:{“build”:{“version”:“1.4.13”,“revision”:“88e67ce987d78ce44de252219e07dc176a3511c2”}}}

info: --> GET /wd/hub/status {}

info: [debug] Responding to client with success: {“status”:0,“value”:{“build”:{“version”:“1.4.13”,“revision”:“88e67ce987d78ce44de252219e07dc176a3511c2”}}}

info: <-- GET /wd/hub/status 200 2.933 ms - 105 {“status”:0,“value”:{“build”:{“version”:“1.4.13”,“revision”:“88e67ce987d78ce44de252219e07dc176a3511c2”}}}

info: --> GET /wd/hub/status {}

info: [debug] Responding to client with success: {“status”:0,“value”:{“build”:{“version”:“1.4.13”,“revision”:“88e67ce987d78ce44de252219e07dc176a3511c2”}}}
info: <-- GET /wd/hub/status 200 0.776 ms - 105 {“status”:0,“value”:{“build”:{“version”:“1.4.13”,“revision”:“88e67ce987d78ce44de252219e07dc176a3511c2”}}}

info: --> GET /wd/hub/status {}

info: [debug] Responding to client with success: {“status”:0,“value”:{“build”:{“version”:“1.4.13”,“revision”:“88e67ce987d78ce44de252219e07dc176a3511c2”}}}
info: <-- GET /wd/hub/status 200 1.027 ms - 105 {“status”:0,“value”:{“build”:{“version”:“1.4.13”,“revision”:“88e67ce987d78ce44de252219e07dc176a3511c2”}}}

info: --> POST /wd/hub/session {“desiredCapabilities”:{“browserName”:“Safari”,“platformName”:“iOS”,“deviceName”:“iPhone 6”,“platformVersion”:“9.0”}}

info: Client User-Agent string: Apache-HttpClient/4.4.1 (Java/1.8.0_60)
info: *************************************
info: *************************************
info: *************************************
info: *************************************
info: *************************************
info: *************************************

info: *************************************
info: *************************************
info: **** NEW SESSION ***
info: **** NEW SESSION ***
info: **** NEW SESSION ***
info: **** NEW SESSION ***
info: **** NEW SESSION ***
info: **** NEW SESSION ***
info: **** NEW SESSION ***
info: **** NEW SESSION ***
info: *************************************
info: *************************************
info: *************************************
info: *************************************
info: *************************************
info: *************************************
info: *************************************
info: *************************************
info: [debug] Configuring Safari session
info: [debug] We’re on iOS8+ so not copying mobile safari app

info: [debug] Creating new appium session bb1ca1e5-cc38-41d6-b430-f210aec905dc

info: [debug] Removing any remaining instruments sockets

info: [debug] Cleaned up instruments socket /tmp/instruments_sock

info: [debug] Setting Xcode version

info: [debug] Xcode version set to 7.0.1

info: [debug] Setting iOS SDK Version

info: [debug] iOS SDK Version set to 9.0

info: [debug] Checking whether instruments supports our device string
info: [debug] Getting list of devices instruments supports

info: [debug] Instruments is at: /Applications/Xcode.app/Contents/Developer/usr/bin/instruments

error: Failed getting devices. Err: Error: Command failed: /bin/sh -c ‘/Applications/Xcode.app/Contents/Developer/usr/bin/instruments’ -s devices
. Stdout: . Stderr: .

info: [debug] Getting list of devices instruments supports

info: [debug] Instruments is at: /Applications/Xcode.app/Contents/Developer/usr/bin/instruments

error: Failed getting devices. Err: Error: Command failed: /bin/sh -c ‘/Applications/Xcode.app/Contents/Developer/usr/bin/instruments’ -s devices
. Stdout: . Stderr: .

info: [debug] Getting list of devices instruments supports

info: [debug] Instruments is at: /Applications/Xcode.app/Contents/Developer/usr/bin/instruments

info: --> GET /wd/hub/status {}

info: [debug] Responding to client with success: {“status”:0,“value”:{“build”:{“version”:“1.4.13”,“revision”:“88e67ce987d78ce44de252219e07dc176a3511c2”},“isShuttingDown”:false},“sessionId”:“bb1ca1e5-cc38-41d6-b430-f210aec905dc”}
info: <-- GET /wd/hub/status 200 1.203 ms - 179 {“status”:0,“value”:{“build”:{“version”:“1.4.13”,“revision”:“88e67ce987d78ce44de252219e07dc176a3511c2”},“isShuttingDown”:false},“sessionId”:“bb1ca1e5-cc38-41d6-b430-f210aec905dc”}

error: Failed getting devices. Err: Error: Command failed: /bin/sh -c ‘/Applications/Xcode.app/Contents/Developer/usr/bin/instruments’ -s devices
. Stdout: . Stderr: .

info: [debug] Cleaning up appium session

error: Failed to start an Appium session, err was: Error: Failed getting devices. Err: Error: Command failed: /bin/sh -c ‘/Applications/Xcode.app/Contents/Developer/usr/bin/instruments’ -s devices
. Stdout: . Stderr: .

info: [debug] Error: Failed getting devices. Err: Error: Command failed: /bin/sh -c ‘/Applications/Xcode.app/Contents/Developer/usr/bin/instruments’ -s devices
. Stdout: . Stderr: .
at /Users/vnvdm/appium/node_modules/appium-instruments/lib/instruments.js:111:19
at ChildProcess.exithandler (child_process.js:758:5)
at ChildProcess.emit (events.js:110:17)
at maybeClose (child_process.js:1015:16)
at Process.ChildProcess._handle.onexit (child_process.js:1087:5)

info: [debug] Responding to client with error: {“status”:33,“value”:{“message”:“A new session could not be created. (Original error: Failed getting devices. Err: Error: Command failed: /bin/sh -c ‘/Applications/Xcode.app/Contents/Developer/usr/bin/instruments’ -s devices\n. Stdout: . Stderr: .)”,“origValue”:“Failed getting devices. Err: Error: Command failed: /bin/sh -c ‘/Applications/Xcode.app/Contents/Developer/usr/bin/instruments’ -s devices\n. Stdout: . Stderr: .”},“sessionId”:null}

info: <-- POST /wd/hub/session 500 37495.693 ms - 444

31

Oh! U too stucked with the simulator issue. Might be this is the Appium 1.4.13 issue with ios 9.0 in simulators then … :frowning:

32

So I guess that’s a “No” on you attempting to contact the teams to see if they are ever going to release updated versions of the .app.

33

@Sean_Conrad they are aware of the release. We don’t have control over their update. Feel free to show your support for the update on the associated issues.

34

I understand they are aware of the release. However, it has been nearly two months since the last release and they have not commented on your request with a release timeline. So I had hoped that you, a member of the Appium Team, could ask them if they were planning on releasing a new version of the .app. That was clearly unrealistic, so I will comment on the github request.

35

Hi Scott,
I encountered these issues while using Appium version 1.4.13.

I’m trying to use one type of install to get both iOS and Android to work.

If I install appium via cloning Git using ./reset.sh , I have issue with installing for Android and it gives error when running iOS Simulators, but runs fine with a real iPhone Device.

If I install appium via npm, I have issue with it not installing SafariLauncher properly for real iOS device, gets error with iOS simulators, and getting an error with running on real Android device, but it runs fine with Android Simulators.

I spent hours on sorting out the issues and logging them into a bug report.

Issues Reported:

I think these are valid issues, but please pardon my unfamiliarity with Appium if these issues ends up being a setup issue. Please let me know how I can fix these issues.

Thank you for your help.

36

Hello, I’m having a problem using the GUI app of Appium, when i start the server I get the following error:

error: uncaughtException: Cannot find module ‘appium-instruments’ date=Mon Oct 12 2015 13:11:25 GMT+0100 (WEST), pid=9985, uid=501, gid=20, cwd=/Applications/Appium.app/Contents/Resources/node_modules/appium, execPath=/Applications/Appium.app/Contents/Resources/node/bin/node, version=v0.12.7, argv=[/Applications/Appium.app/Contents/Resources/node/bin/node, /Applications/Appium.app/Contents/Resources/node_modules/appium/lib/server/main.js, --command-timeout, 7200, --debug-log-spacing, --platform-version, 8.1, --platform-name, iOS, --app, /Users/manaljazouli/Downloads/screendy.app, --full-reset, --show-ios-log, --device-name, iPhone 6], rss=77594624, heapTotal=61778432, heapUsed=26590200, loadavg=[1.779296875, 1.46630859375, 1.45458984375], uptime=83202, trace=[column=15, file=module.js, function=Function.Module._resolveFilename, line=336, method=Module._resolveFilename, native=false, column=25, file=module.js, function=Function.Module._load, line=278, method=Module._load, native=false, column=17, file=module.js, function=Module.require, line=365, method=require, native=false, column=17, file=module.js, function=require, line=384, method=null, native=false, column=14, file=/Applications/Appium.app/Contents/Resources/node_modules/appium/lib/devices/ios/instruments.js, function=, line=4, method=null, native=false, column=26, file=module.js, function=Module._compile, line=460, method=_compile, native=false, column=10, file=module.js, function=Object.Module._extensions…js, line=478, method=Module._extensions…js, native=false, column=32, file=module.js, function=Module.load, line=355, method=load, native=false, column=12, file=module.js, function=Function.Module._load, line=310, method=Module._load, native=false, column=17, file=module.js, function=Module.require, line=365, method=require, native=false, column=17, file=module.js, function=require, line=384, method=null, native=false, column=19, file=/Applications/Appium.app/Contents/Resources/node_modules/appium/lib/devices/ios/ios.js, function=, line=15, method=null, native=false, column=26, file=module.js, function=Module._compile, line=460, method=_compile, native=false, column=10, file=module.js, function=Object.Module._extensions…js, line=478, method=Module._extensions…js, native=false, column=32, file=module.js, function=Module.load, line=355, method=load, native=false, column=12, file=module.js, function=Function.Module._load, line=310, method=Module._load, native=false], stack=[Error: Cannot find module ‘appium-instruments’, at Function.Module._resolveFilename (module.js:336:15), at Function.Module._load (module.js:278:25), at Module.require (module.js:365:17), at require (module.js:384:17), at Object. (/Applications/Appium.app/Contents/Resources/node_modules/appium/lib/devices/ios/instruments.js:4:14), at Module._compile (module.js:460:26), at Object.Module._extensions…js (module.js:478:10), at Module.load (module.js:355:32), at Function.Module._load (module.js:310:12), at Module.require (module.js:365:17), at require (module.js:384:17), at Object. (/Applications/Appium.app/Contents/Resources/node_modules/appium/lib/devices/ios/ios.js:15:19), at Module._compile (module.js:460:26), at Object.Module._extensions…js (module.js:478:10), at Module.load (module.js:355:32), at Function.Module._load (module.js:310:12)]

37

Happy Monday! You can finally download a .DMG for the 1.4.13 Mac app directly from the download page. http://appium.io/

Note that autoupdate is not setup to fetch the new version at the time I write this. You should download and install manually from the webpage.

Awwwww, got too excited. It throws an unrecoverable error “uncaughtException: Cannot find module ‘appium-instruments’” and won’t run. https://github.com/appium/appium-dot-app/issues/510

3 Likes
39

I follwed these instructions :slightly_smiling:
http://www.6020peaks.com/2016/02/mobile-automation-testing-for-android-with-appium/

At this point, I am getting error message :

karthik@dkarnik2-Vostro-3558:~/latestappium$ git clone git://github.com/appium/appium.git
Cloning into ‘appium’…
remote: Counting objects: 37387, done.
remote: Compressing objects: 100% (90/90), done.
remote: Total 37387 (delta 35), reused 0 (delta 0), pack-reused 37297
Receiving objects: 100% (37387/37387), 36.15 MiB | 132.00 KiB/s, done.
Resolving deltas: 100% (23726/23726), done.
Checking connectivity… done.
karthik@dkarnik2-Vostro-3558:~/latestappium$ cd appium
karthik@dkarnik2-Vostro-3558:~/latestappium/appium$ ./reset.sh —android --verbose
bash: ./reset.sh: No such file or directory
karthik@dkarnik2-Vostro-3558:~/latestappium/appium$ ls
AUTHORS CHANGELOG.md CONTRIBUTING.md GOVERNANCE.md lib npm-shrinkwrap.json packweb.json RELEASE.pdf test
bin CONDUCT.md docs gulpfile.js LICENSE package.json README.md ROADMAP.md
karthik@dkarnik2-Vostro-3558:~/latestappium/appium$

There is no reset.sh file in appium… What am i supposed to do now ?? How can i install Appium ??

40

+1 on this issue. reset.sh seems to be missing from Github right now…

https://github.com/appium/appium/blob/master/reset.sh

41

@Karthik_Uppoor, @kim-klask

I think the dependencies of Appium have been moved out of the project into individual NPM packages. If I understood the project correctly, the reset.sh script was for ensuring Appium’s dependencies were present.

To set up Appium’s dependencies now, you can run “npm install” inside Appium’s project directory now. NPM should read the package.json file and install the dependencies from there.

1 Like