This site is in read only mode. Please continue to browse, but replying, likes, and other actions are disabled for now.
Oct 2014
1 / 22
Oct 2014
Nov 2014
jonahss
Oct '14

There was a bug in v1.3.0 that nobody seems to have run into yet, except for us :smile: This release is to correct that.

Not a major change, but I suggest updating, especially if you run on Sauce Labs.

CHANGES IN VERSION 1.3.1 (from 1.3.0)

iOS

  • fixed a bug where appium could hang if the 'full-reset' and 'keepKeychain' capabilities were both used on ios8.1
  • default context now set to NATIVE_APP instead of being null

Android

  • fix bugs which arise from spaces in the path to adb tool
  • fix detection of whether the screen is locked
  • fix an error with running remote apk's on Windows

  • created

    Oct '14

  • last reply

    Nov '14
  • 21

    replies

  • 3.7k

    views

  • 11

    users

  • 7

    likes

  • 3

    links

pinned globally Oct 24, '14

SinghP5411
Oct '14

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 .

SinghP5411
Oct '14

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

Ramon_Cidade
Oct '14

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?

Patrick_Shay
Oct '14

@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.

SinghP5411
Oct '14

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 .

Patrick_Shay
Oct '14

@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.

jonahss
Nov '14
SinghP5411

No changes to xpath in this version. You might want to make sure your xpath expression gets the element you want. As always, the suggested flow for writing tests is to open an interactive session in a repl and build up valid xpath expressions until you find one that gets the element you want.

SinghP5411
Nov '14

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 :smiley: . I have to quit appium dmg in intervals to cool off my system .

sendlink
Nov '14

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

Mayuresh_Shirodkar
Nov '14

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"}