Appium 1.3.1 released

.dmg?? Where can I find it?

I am running 1.3.1 dmg now and it seems to hang every time i try to use locator in inspector . Also my CPU utilisation seems to drastically increase .

Also it does not find element by xpath even though i copied xpath from appium GUI itself .

Since 1.3 whenever I try to use the language capability I get the error "Appium was unable to set locale info: Error: Settings file /Users/srv_teste_aut_hmg/Library/Developer/CoreSimulator/Devices/26243EFA-2F9E-4D21-95F5-0D2C6F441474/data/Library/Preferences/.GlobalPreferences.plist did not exist". I can't set the language so my tests failing.
Somebody has a clue of what can be happening?

@SinghP5411 what environment are you developing for/with? I am writing tests for iOS in java, and I have found that xpath is unreliable for identifying UI elements. It will sometimes drop support with no warning/ no answers. I highly suggest you find a different way to access your screen elements. For iOS, I identify web elements using Accessibility Id's.

I am trying to launch inspector from appium GUI and then i copy xpath that is shown in inspector and try to search it again using locator option in GUI . It used to work perfectly well with previous appium GUI and with this one it doesnt .

When can we expect .exe for 1.3.1

@raghuappium have you checked appium.io? I believe it is already out.

@SinghP5411 I know that appium uses xpath by default, but you should really move away from it. You will not always be able to depend on xpath to work, and I was left in your situation a couple months ago. Again, I learned to access web elements by Accessibility ID, and that has worked for my iOS tests. That method has not broken, while Xpath is down once again.

Thanks for sharing this .

"Quiet Logging" is not working

Thanks Jon .

I have started using identifiers for most of the places and for now able to proceed in my project . There is another thing that is worrying me is whenever i launch appium dmg , CPU Utilization goes so high and seems like my laptop is on fire . I have to quit appium dmg in intervals to cool off my system .

@jonahss Send keys is not working in appium 1.3.1 issue is not observed when used appium 1.2.4
Please refer

When i use the by name strategy is not working for me in native context.
I m using xcode 6.0 on iOS 8.0.2 iPhone. Appium 1.3.1.

The logs i get are similar
fo: [debug] Pushing command to appium work queue: "au.getElementByName('New Email')"
info: [debug] Sending command to instruments: au.getElementByName('New Email')
info: [debug] [INST] 2014-11-05 10:07:32 +0000 Debug: Got new command 44 from instruments: au.getElementByName('New Email')
info: [debug] [INST] 2014-11-05 10:07:32 +0000 Debug: evaluating au.getElementByName('New Email')
info: [debug] [INST] 2014-11-05 10:07:32 +0000 Debug: evaluation finished
info: [debug] [INST] 2014-11-05 10:07:32 +0000 Debug: responding with:
info: [debug] [INST]
2014-11-05 10:07:32 +0000 Debug: Running system command #45:
/usr/local/Cellar/node/0.10.28/bin/node
/Users/student/appium/submodules/appium-uiauto/bin/command-proxy-client.js
/tmp/instruments_sock 2,{"status":0,"value":""}...
info: [debug] Socket data received (25 bytes)
info: [debug] Socket data being routed.
info: [debug] Got result from instruments: {"status":0,"value":""}
info: [debug] Condition unmet after 3183ms. Timing out.
info:
[debug] Responding to client with error:
{"status":7,"value":{"message":"An element could not be located on the
page using the given search
parameters.","origValue":""},"sessionId":"a2175e11-f742-4834-b429-4e26a87b0dc6"}